http-cache-semantics max-stale handling can disclose cross-user cached responses
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.
GHSA-ch52-4w7c-c8xp
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: osv:GHSA-ch52-4w7c-c8xp
http-cache-semantics
Source reference: /affected/0/package/name
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"last_affected": "4.2.0"
}
]
}
],
"package": {
"name": "http-cache-semantics",
"purl": "pkg:npm/http-cache-semantics",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/09/GHSA-ch52-4w7c-c8xp/GHSA-ch52-4w7c-c8xp.json"
}
}
]- Related CVEs
- CVE-2026-93748
Source reference:
/aliases
Publisher severity
high
Source reference: /database_specific/severity
- Event
- #71362 · Revision 1
- Added to Heist Feed
- Publisher date