CVE-2026-93748
http-cache-semantics through 4.2.0 fails to properly validate …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/kornelski/http-cache-semantics
- github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633ba880e5e980aa54c/in
- github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633ba880e5e980aa54c/in
- github.com/kornelski/http-cache-semantics/issues/56
- www.vulncheck.com/advisories/http-cache-semantics-through-4.2.0-cross-user-cache-disclosur
- nvd.nist.gov/vuln/detail/CVE-2026-93748
- github.com/advisories/GHSA-ch52-4w7c-c8xp
- github.com/kornelski/http-cache-semantics/issues/56#issuecomment-5975759591
- nvd.nist.gov/vuln/detail/CVE-2026-93748
- cve.org/CVERecord?id=CVE-2026-93748
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.