How to fix: Cache-Control: public on sensitive resource
A response containing authenticated or user-specific content is served with Cache-Control: public, allowing it to be cached by shared proxies.
Why it matters
Caching authenticated responses at shared proxy caches (CDNs, corporate proxies) means one user's private data may be served to another user, a critical data leakage vulnerability.
Authenticated and user-specific responses must use Cache-Control: private or no-store to prevent shared caching.
How to fix it
- 1Change Cache-Control to "no-store" for authenticated/private responses
- 2Use "private, no-cache" for responses that vary per user but can be re-validated
- 3Review your CDN configuration to ensure it does not cache authenticated routes
Code examples
Correct for authenticated responses
return Response.json(userData, {
headers: { "Cache-Control": "no-store, max-age=0" }
});
// Never use "public" for authenticated or user-specific dataReferences
Detected automatically by VulnRadar. The check id is cache-control-public-sensitive, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Cache-Control: public on sensitive resource?
- VulnRadar rates this high 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 cache-control-public-sensitive, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Cache-Control: public on sensitive resource map to?
- It maps to CWE-525. In the OWASP Top 10 it falls under A04: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.