http-cache-semantics 4.2.0 Cache Credential Leakage via maxstale
CVE-2026-93748 Published on September 18, 2026
http-cache-semantics through 4.2.0 Cross-User Cache Disclosure via max-stale
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.
Vulnerability Analysis
CVE-2026-93748 is exploitable with network access, and does not require authorization privileges or user interaction. This vulnerability is considered to have a low attack complexity. The potential impact of an exploit of this vulnerability is considered to have no impact on confidentiality and integrity and availability.
Weakness Type
Use of Cache Containing Sensitive Information
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere. Applications may use caches to improve efficiency when communicating with remote entities or performing intensive calculations. A cache maintains a pool of objects, threads, connections, pages, financial data, passwords, or other resources to minimize the time it takes to initialize and access these resources. If the cache is accessible to unauthorized actors, attackers can read the cache and obtain this sensitive information.
Products Associated with CVE-2026-93748
Want to know whenever a new CVE is published for Http Cache Semanticsproject Http Cache Semantics? stack.watch will email you.
Affected Versions
kornelski http-cache-semantics:- Before and including 4.2.0 is affected.