Skip to main content
InfoHeadersOWASP A05:2021CWE-693

How to fix: Permissions-Policy microphone allowed

Microphone should default to 'self' or be blocked.

Why it matters

Set Permissions-Policy: microphone=() to block entirely

Microphone should default to 'self' or be blocked.

How to fix it

  1. 1Set Permissions-Policy: microphone=() to block entirely

Code examples

Restrict microphone in Permissions-Policy

JavaScript
// next.config.mjs
export default {
  async headers() {
    return [{ source: "/(.*)", headers: [{ key: "Permissions-Policy", value: "microphone=('self')" }] }];
  },
};
// Only allow your own origin to request microphone permission

References

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

See every headers check

Questions

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