How to fix: Unsafe Referrer-Policy Value
Referrer-Policy uses a value that leaks full URLs.
Why it matters
Full URLs including query params leaked to third parties.
unsafe-url and no-referrer-when-downgrade send full referrer to all destinations.
How to fix it
- 1Use strict-origin-when-cross-origin or no-referrer.
Code examples
Set a safe Referrer-Policy
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Referrer-Policy", value: "strict-origin-when-cross-origin" }] }];
},
};
// strict-origin-when-cross-origin sends the full URL for same-origin requests
// and only the origin for cross-origin HTTPS requests, nothing for HTTP downgradesReferences
Detected automatically by VulnRadar. The check id is referrer-policy-unsafe, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Unsafe Referrer-Policy Value?
- VulnRadar rates this medium 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-unsafe, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Unsafe Referrer-Policy Value 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.