How to fix: Cross-Origin-Opener-Policy Explicitly Set to unsafe-none
The Cross-Origin-Opener-Policy header is explicitly set to 'unsafe-none', which opts the page out of browsing-context isolation.
Why it matters
Without COOP isolation, a malicious popup or cross-origin window can retain a reference to this page via window.opener and probe it for cross-window (XS-Leaks) side-channel attacks.
'unsafe-none' is the pre-COOP legacy default that keeps window.opener references alive across origins. Setting it explicitly (rather than simply omitting the header) usually means isolation was deliberately turned off, often to support a legacy popup-based OAuth or payment flow.
How to fix it
- 1Set Cross-Origin-Opener-Policy: same-origin unless a specific cross-origin popup flow requires opener access.
- 2If a popup flow needs partial isolation, use same-origin-allow-popups instead of unsafe-none.
- 3Migrate any window.opener-based communication to postMessage with explicit origin checks.
Code examples
Next.js
const nextConfig = {
async headers() {
return [{
source: '/(.*)',
headers: [{ key: 'Cross-Origin-Opener-Policy', value: 'same-origin' }],
}];
},
};
export default nextConfig;Nginx
add_header Cross-Origin-Opener-Policy "same-origin" always;References
Detected automatically by VulnRadar. The check id is coop-unsafe-none, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Cross-Origin-Opener-Policy Explicitly Set to unsafe-none?
- 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 coop-unsafe-none, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Cross-Origin-Opener-Policy Explicitly Set to unsafe-none map to?
- It maps to CWE-693. 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.