How to fix: Missing Cross-Origin-Resource-Policy (CORP)
No Cross-Origin-Resource-Policy header is set.
Why it matters
Your resources can be embedded by any origin.
CORP complements COOP and COEP to enable cross-origin isolation.
How to fix it
- 1Add 'Cross-Origin-Resource-Policy: same-origin' for maximum protection.
- 2Use 'same-site' if resources need to be shared across subdomains.
- 3Use 'cross-origin' only for public CDN assets.
Code examples
Next.js
const nextConfig = { async headers() { return [{ source: '/(.*)', headers: [{ key: 'Cross-Origin-Resource-Policy', value: 'same-origin' }] }]; } };References
Detected automatically by VulnRadar. The check id is cross-origin-resource-policy-report-only-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Missing Cross-Origin-Resource-Policy (CORP)?
- 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 cross-origin-resource-policy-report-only-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Missing Cross-Origin-Resource-Policy (CORP) 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.