How to fix: Referrer-Policy not set to strict-origin-when-cross-origin
The Referrer-Policy header is absent or not set to a strict value, potentially leaking full URL referrers to cross-origin destinations.
Why it matters
Without a strict Referrer-Policy, the full URL of pages (including query strings with tokens, user IDs, or search terms) is sent in the Referer header to every third-party origin, leaking user activity and potentially sensitive URL parameters.
strict-origin-when-cross-origin is the recommended value: it sends the full URL for same-origin requests but only the origin for cross-origin HTTPS requests.
How to fix it
- 1Add Referrer-Policy: strict-origin-when-cross-origin to all responses
Code examples
Next.js
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Referrer-Policy", value: "strict-origin-when-cross-origin" }] }];
},
};References
Detected automatically by VulnRadar. The check id is referrer-policy-no-referrer-strict-origin-when-cross-origin, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Referrer-Policy not set to strict-origin-when-cross-origin?
- 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 referrer-policy-no-referrer-strict-origin-when-cross-origin, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Referrer-Policy not set to strict-origin-when-cross-origin map to?
- It maps to CWE-200. In the OWASP Top 10 it falls under A05: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.