How to fix: X-Netlify-Cache Exposes CDN Cache State
Netlify's X-Netlify-Cache header exposes HIT/MISS/PASS/REVALIDATE cache status on responses, confirming Netlify infrastructure usage.
Why it matters
Confirms Netlify as the hosting platform, helping attackers target Netlify-specific misconfigurations (redirect rules, identity misconfiguration, function endpoint enumeration).
X-Netlify-Cache is added by Netlify's CDN layer for debugging purposes. In production, it provides no user value and leaks CDN infrastructure identity.
How to fix it
- 1Add a custom response header rule in netlify.toml or the Netlify UI to strip X-Netlify-Cache.
- 2Use a Netlify Edge Function to delete the header.
Code examples
netlify.toml
[[headers]]
for = "/*"
[headers.values]
X-Netlify-Cache = ""
# Note: Netlify does not support header deletion via toml; use an edge function insteadReferences
Detected automatically by VulnRadar. The check id is x-netlify-cache, stable across every scan so you can filter or diff on it.
More config checks
- MediumNo Rate-Limit Policy Detected
- MediumVary: Cookie Missing on Cookie-Bearing Response
- LowSet-Cookie Header Exceeds 4 KB
- LowVary Header Missing on Compressed Responses
- InfoDownloadable Content Served as inline
- InfoX-XSS-Protection Header Is Deprecated
- LowServer-Timing Exposes Cache Timings
- LowVary: Cookie on Static Resource
Questions
- How severe is X-Netlify-Cache Exposes CDN Cache State?
- VulnRadar rates this info severity in the config 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 x-netlify-cache, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does X-Netlify-Cache Exposes CDN Cache State map to?
- It maps to CWE-200. 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.