How to fix: Deprecated Feature-Policy header in use
The Feature-Policy header is present. This header has been replaced by Permissions-Policy.
Why it matters
Feature-Policy is no longer supported in modern browsers. Relying on it means your feature restrictions may be silently ignored, leaving the page without the intended browser feature controls.
Feature-Policy was renamed to Permissions-Policy in 2020. Use Permissions-Policy instead.
How to fix it
- 1Replace the Feature-Policy header with Permissions-Policy
- 2Update the directive syntax (Permissions-Policy uses a different format)
- 3Remove the Feature-Policy header entirely once Permissions-Policy is set
Code examples
Migrate to Permissions-Policy
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Permissions-Policy", value: "camera=(), microphone=(), geolocation=(), payment=()" }] }];
},
};References
Detected automatically by VulnRadar. The check id is feature-policy-deprecated, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Deprecated Feature-Policy header in use?
- 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 feature-policy-deprecated, which stays the same between runs so you can filter, diff, or gate CI on it.
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.