Skip to main content
InfoHeadersOWASP A05:2021CWE-693

How to fix: Permissions-Policy Browsing-Topics allowed

Permissions-Policy does not block the browsing-topics directive, leaving Chrome's Privacy Sandbox Topics API available to any script on the page.

Why it matters

With browsing-topics left enabled, third-party scripts embedded on the page (ads, widgets) can call document.browsingTopics() and read the browser's inferred interest categories for this visitor, without an explicit opt-in from the site.

The Topics API replaced FLoC as Chrome's cohort-based interest-tracking mechanism. Sites that don't intend to participate should explicitly disable it via Permissions-Policy, the same way the earlier interest-cohort directive was recommended for FLoC.

How to fix it

  1. 1Set Permissions-Policy: browsing-topics=()

Code examples

Block the Topics API in Permissions-Policy

JavaScript
// next.config.mjs
export default {
  async headers() {
    return [{ source: "/(.*)", headers: [{ key: "Permissions-Policy", value: "browsing-topics=()" }] }];
  },
};
// Disables Chrome's Privacy Sandbox Topics API for this page

References

Detected automatically by VulnRadar. The check id is permissions-policy-browsing-topics-blocked, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Permissions-Policy Browsing-Topics 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-browsing-topics-blocked, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Permissions-Policy Browsing-Topics 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.

Propose a checkHow a check is built

Scan your own site for permissions-policy browsing-topics allowed

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Permissions-Policy Browsing-Topics allowed fix | VulnRadar