How to fix: X-Content-Type-Options set to an invalid value
The X-Content-Type-Options header is present but set to a value other than "nosniff", making it ineffective.
Why it matters
An incorrect value like X-Content-Type-Options: true or X-Content-Type-Options: 1 is ignored by browsers, leaving MIME sniffing enabled and the page vulnerable to content-type confusion attacks.
The only valid value for X-Content-Type-Options is "nosniff" (lowercase).
How to fix it
- 1Set X-Content-Type-Options: nosniff (the only valid value)
- 2Remove any other value you may have set
Code examples
Correct value
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "X-Content-Type-Options", value: "nosniff" }] }];
},
};References
Detected automatically by VulnRadar. The check id is nosniff-incorrect, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is X-Content-Type-Options set to an invalid value?
- VulnRadar rates this medium 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 nosniff-incorrect, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does X-Content-Type-Options set to an invalid value 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.