HIGH7.5
GHSA-ch52-4w7c-c8xp
http-cache-semantics max-stale handling can disclose cross-user cached responses
Details
http-cache-semantics through 4.2.0 fails to properly validate security-zeroed cache entries when processing client max-stale directives, allowing unauthenticated attackers to retrieve cached responses belonging to other users. Attackers can request the same URL with a large max-stale value to obtain another user's Set-Cookie session credentials from shared-cache entries that were deliberately zeroed for security reasons.
Are you affected?
Enter the version of the package you're using.
Affected packages
npm/http-cache-semantics
Introduced in:
0No fixed version published yet for http-cache-semantics (npm). Pin to a known-safe version or switch to an alternative.
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-93748[ADVISORY]
- https://github.com/kornelski/http-cache-semantics/issues/56[WEB]
- https://github.com/kornelski/http-cache-semantics[PACKAGE]
- https://github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633ba880e5e980aa54c/index.js#L425-L441[WEB]
- https://github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633ba880e5e980aa54c/index.js#L603-L623[WEB]
- https://www.vulncheck.com/advisories/http-cache-semantics-through-4.2.0-cross-user-cache-disclosure-via-max-stale[WEB]