How to fix: Missing X-Content-Type-Options header
The server does not send the X-Content-Type-Options: nosniff header, allowing browsers to guess content types.
Why it matters
Without nosniff, browsers may interpret a response with an unexpected content type as executable, enabling MIME confusion attacks where a text file is loaded as a script or HTML document.
X-Content-Type-Options: nosniff tells browsers to strictly follow the declared Content-Type and not try to guess it from content.
How to fix it
- 1Add X-Content-Type-Options: nosniff to all responses
- 2Ensure all resources are served with correct Content-Type headers
Code examples
Next.js
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "X-Content-Type-Options", value: "nosniff" }] }];
},
};Nginx
add_header X-Content-Type-Options "nosniff" always;References
Detected automatically by VulnRadar. The check id is xcto-missing, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Missing X-Content-Type-Options header?
- 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 xcto-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Missing X-Content-Type-Options header 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.