Cross-client response disclosure via Vary wildcard miscomparison
Published Sep 18, 2026 · Updated Sep 18, 2026
Cache validation failure in http-cache-semantics 4.2.0 and earlier allows remote attackers to read other clients' cached responses. The _varyMatches() function compares Vary against a byte-exact wildcard, then treats trimmed or prototype-derived field values as matching. Exploitation requires a shared cache and origin-reachable noncanonical Vary formatting; the reported consequence is cross-client response disclosure.
Summary
What happened
Cache validation failure in http-cache-semantics 4.2.0 and earlier allows remote attackers to read other clients' cached responses. The _varyMatches() function compares Vary against a byte-exact wildcard, then treats trimmed or prototype-derived field values as matching. Exploitation requires a shared cache and origin-reachable noncanonical Vary formatting; the reported consequence is cross-client response disclosure.
The record
- CVE
- CVE-2026-93750
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- Kornel Lesiński
- Product
- http-cache-semantics
- Classifications
- CWE-436
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=4.2.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- GitHub Issue #57 trigger casesproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started