How to fix: Permissions-Policy interest-cohort allowed
Permissions-Policy does not block the legacy interest-cohort directive (FLoC).
Why it matters
On browsers that still recognize the legacy FLoC directive, third-party scripts could read the page's cohort assignment.
interest-cohort was the original Permissions-Policy directive for opting out of FLoC before it was renamed to browsing-topics. Some scanners and older browser builds still check for it, so it's worth disabling explicitly alongside browsing-topics.
How to fix it
- 1Set Permissions-Policy: interest-cohort=()
Code examples
Block legacy FLoC directive
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Permissions-Policy", value: "interest-cohort=(), browsing-topics=()" }] }];
},
};References
Detected automatically by VulnRadar. The check id is permissions-policy-interest-cohort-blocked, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Permissions-Policy interest-cohort allowed?
- 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 permissions-policy-interest-cohort-blocked, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Permissions-Policy interest-cohort allowed 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.