How to fix: COOP Report-Only Without Enforcement
Cross-Origin-Opener-Policy-Report-Only is set but no enforcing Cross-Origin-Opener-Policy header exists.
Why it matters
The site is only logging what COOP would have blocked, not actually isolating the browsing context, so window.opener-based XS-Leaks attacks remain possible.
Cross-Origin-Opener-Policy-Report-Only is meant for testing before deployment, the same way CSP-Report-Only is. Running it indefinitely without a matching enforcing header means zero isolation is ever applied.
How to fix it
- 1Deploy an enforcing Cross-Origin-Opener-Policy header alongside the report-only one.
- 2Start with same-origin-allow-popups if a popup flow depends on opener access, then tighten to same-origin.
Code examples
Both headers
Cross-Origin-Opener-Policy: same-origin
Cross-Origin-Opener-Policy-Report-Only: same-origin; report-to="coop-endpoint"References
Detected automatically by VulnRadar. The check id is coop-report-only-without-enforcing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is COOP Report-Only Without Enforcement?
- 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 coop-report-only-without-enforcing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does COOP Report-Only Without Enforcement 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.