CVE-2026-93748: http-cache-semantics max-stale handling can disclose cross-user cached responses
(updated )
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.
References
- github.com/advisories/GHSA-ch52-4w7c-c8xp
- github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633ba880e5e980aa54c/index.js
- github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633ba880e5e980aa54c/index.js
- github.com/kornelski/http-cache-semantics/issues/56
- nvd.nist.gov/vuln/detail/CVE-2026-93748
- www.vulncheck.com/advisories/http-cache-semantics-through-4.2.0-cross-user-cache-disclosure-via-max-stale
Code Behaviors & Features
Detect and mitigate CVE-2026-93748 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →