How to fix: CSP missing upgrade-insecure-requests directive
The Content-Security-Policy header does not include upgrade-insecure-requests, leaving HTTP sub-resources unprotected.
Why it matters
Without upgrade-insecure-requests, HTTP URLs for images, scripts, and other resources are not automatically upgraded to HTTPS, enabling mixed content attacks that downgrade connections.
The upgrade-insecure-requests directive instructs browsers to treat all HTTP resource requests as HTTPS.
How to fix it
- 1Add upgrade-insecure-requests to your CSP header
- 2Verify your CSP does not also include block-all-mixed-content (pick one)
Code examples
Add to existing CSP
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Content-Security-Policy", value: "upgrade-insecure-requests; default-src 'self'; script-src 'self'; object-src 'none';" }] }];
},
};References
Detected automatically by VulnRadar. The check id is csp-no-upgrade-insecure, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is CSP missing upgrade-insecure-requests directive?
- VulnRadar rates this low severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id csp-no-upgrade-insecure, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does CSP missing upgrade-insecure-requests directive map to?
- It maps to CWE-319. In the OWASP Top 10 it falls under A02:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.