How to fix: Access-Control-Expose-Headers lists many response headers
Access-Control-Expose-Headers lists five or more entries, exposing a large number of response headers to cross-origin JavaScript.
Why it matters
Exposing many headers increases the chance that internal routing headers, server version info, or other metadata not meant to be public is readable by any cross-origin page that has CORS access.
Only list the specific headers that cross-origin clients actually need to read; a long list often means headers were added without review.
How to fix it
- 1Review the list and remove any headers cross-origin clients don't need
- 2Never include headers like Set-Cookie, Authorization, or internal headers in the list
- 3Avoid a blanket wildcard (*) value as well
Code examples
Explicit header list
headers["Access-Control-Expose-Headers"] = "Content-Length, X-Total-Count";
// Not: Access-Control-Expose-Headers: *References
Detected automatically by VulnRadar. The check id is access-control-expose-broad, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Access-Control-Expose-Headers lists many response headers?
- VulnRadar rates this low 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 access-control-expose-broad, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Access-Control-Expose-Headers lists many response headers 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.