How to fix: Missing Cross-Origin-Opener-Policy (COOP) Header
No Cross-Origin-Opener-Policy header is set. The detector checks for the real, enforcing header, not the optional Report-Only preview variant.
Why it matters
Without COOP, cross-origin windows opened by or opening this page can retain a reference via window.opener, which weakens isolation and can enable Spectre-style side-channel attacks.
Cross-Origin-Opener-Policy: same-origin isolates the page's browsing context from cross-origin windows it opens or that open it. Combined with COEP, it enables cross-origin isolation (SharedArrayBuffer, high-resolution timers).
How to fix it
- 1Add Cross-Origin-Opener-Policy: same-origin to responses.
- 2Use same-origin-allow-popups if the page needs to open popups while staying isolated.
- 3Preview with Cross-Origin-Opener-Policy-Report-Only first if you're unsure it's safe to enable.
Code examples
Add Cross-Origin-Opener-Policy header
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Cross-Origin-Opener-Policy", value: "same-origin" }] }];
},
};
// same-origin: isolates your browsing context from cross-origin windows
// Enables SharedArrayBuffer and high-resolution timers (required for some APIs)
// same-origin-allow-popups: allows popups but isolates main pageReferences
Detected automatically by VulnRadar. The check id is coop-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Missing Cross-Origin-Opener-Policy (COOP) Header?
- VulnRadar rates this info 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-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Missing Cross-Origin-Opener-Policy (COOP) Header 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.