Skip to main content
VulnerabilityPublished Updated

CVE-2026-93748: kornelski http-cache-semantics · Use of Cache Containing Sensitive Information

Affects kornelski http-cache-semanticsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High.

Data as of 2 Nov 2026, 10:58 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
kornelskihttp-cache-semanticsAffected
  • <=4.2.0
Fixed in–
npmhttp-cache-semanticspkg:npm/http-cache-semanticsOther threatsAffected
  • <=4.2.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, avoid using vulnerable versions or restrict access to the caching service to trusted clients only.

Description

A vulnerability in http-cache-semantics up to version 4.2.0 allows unauthenticated attackers to retrieve cached responses containing sensitive information from other users. This occurs because the software fails to properly validate security-zeroed cache entries when processing client max-stale directives. Attackers can exploit this by requesting the same URL with a large max-stale value to obtain another user's Set-Cookie session credentials from shared cache entries.

References

Community reviews

Loading reviews…