How to fix: Missing Cross-Origin-Embedder-Policy header
The response lacks a Cross-Origin-Embedder-Policy (COEP) header, which is required for cross-origin isolation.
Why it matters
Without COEP, the page cannot achieve cross-origin isolation, which blocks access to high-resolution timers, SharedArrayBuffer, and other APIs that depend on isolation, and leaves the page potentially exposed to Spectre-class side-channel attacks.
COEP requires all loaded resources to explicitly opt into cross-origin sharing via CORP or CORS headers.
How to fix it
- 1Add Cross-Origin-Embedder-Policy: require-corp to responses
- 2Also add Cross-Origin-Opener-Policy: same-origin for full isolation
- 3Ensure all embedded cross-origin resources serve CORP or CORS headers
Code examples
Next.js
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Cross-Origin-Embedder-Policy", value: "require-corp" }] }];
},
};References
Detected automatically by VulnRadar. The check id is coep-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Missing Cross-Origin-Embedder-Policy 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 coep-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Missing Cross-Origin-Embedder-Policy 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.