CVE-2026-93750

http-cache-semantics through 4.2.0 Cross-Client Cache Disclosure via Vary Wildcard

Published Sep 18, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
http-cache-semantics through 4.2.0 contains a cache validation vulnerability in the _varyMatches() function that fails to properly validate Vary header wildcards due to byte-for-byte string comparison. Attackers can request URLs previously fetched by other clients to receive cached responses intended for different users, disclosing sensitive information across clients.

Analysis

AI-generated

Technical impact

The http-cache-semantics library, used under the identifier kornelski/http-cache-semantics, contains a flaw in its _varyMatches() cache validation routine. The code compares Vary header wildcards using a simple byte‑for‑byte match, which fails to differentiate requests that should point to distinct cached items. As a result an attacker can trigger a request that retrieves a cached response previously fetched for a different client, thereby exposing sensitive information that was not intended for the requester's session. This vulnerability is classified as CWE-436 and CWE-524.

Affected Systems

Any software component or service that relies on the npm package kornelski/http-cache-semantics up to and including version 4.2.0 incorporates this flaw. The vulnerability is present in the library itself, so all installations of the package in that version range are affected. No information indicates that later releases fixed the issue, so absence of an update cannot be assumed to mitigate the problem.

Risk and Exploitability

The CVSS score of 8.2 reflects a high severity vulnerability. In contrast, the EPSS score of less than 1 percent indicates that, as of now, exploitation is considered unlikely, though the potential impact remains significant. The flaw is not listed in CISA’s KEV catalogue. Attackers would need the ability to send HTTP requests to a web service that incorporates this package; by first allowing a legitimate client to create a cache entry and then making a subsequent request, an attacker can receive a cached response intended for that original client.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the http-cache-semantics package to the latest released version if an update is available.
  • Avoid caching responses that include a Vary: * header; use explicit header values or disable caching for sensitive resources.
  • Implement a validation layer that verifies that the cached response’s Vary header matches the incoming request’s headers before returning the cached data.

Generated by OpenCVE AI on September 23, 2026 at 02:36 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Kornelski
Kornelski http-cache-semantics
Vendors & Products Kornelski
Kornelski http-cache-semantics
Type Values Removed Values Added
Description http-cache-semantics through 4.2.0 contains a cache validation vulnerability in the _varyMatches() function that fails to properly validate Vary header wildcards due to byte-for-byte string comparison. Attackers can request URLs previously fetched by other clients to receive cached responses intended for different users, disclosing sensitive information across clients.
Title http-cache-semantics through 4.2.0 Cross-Client Cache Disclosure via Vary Wildcard
First Time appeared Http-cache-semantics Project
Http-cache-semantics Project http-cache-semantics
Weaknesses CWE-436
CPEs cpe:2.3:a:http-cache-semantics_project:http-cache-semantics:*:*:*:*:*:*:*:*
Vendors & Products Http-cache-semantics Project
Http-cache-semantics Project http-cache-semantics
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Weaknesses
  • CWE-436

    Interpretation Conflict

  • CWE-524

    Use of Cache Containing Sensitive Information

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 24, 2026, 2:23 PM
Reserved
Sep 18, 2026, 4:30 PM
Status
Deferred
Published
Sep 18, 2026, 6:18 PM
Modified
Sep 23, 2026, 5:17 PM
Severity
Moderate
Public date
Sep 18, 2026, 5:51 PM