CVE-2026-93748

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-18. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 18, 2026

Last Modified

September 18, 2026

Advisory Details (5)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

http-cache-semantics through 4.2.0 Cross-User Cache Disclosure via max-stale | Advisories | VulnCheck

https://www.vulncheck.com/advisories/http-cache-semantics-through-4.2.0-cross-user-cache-disclosure-via-max-stale
generic🟡 PoC Available

Security Advisory: `max-stale` request directive overrides shared-cache reuse prohibitions (Set-Cookie, proxy-revalidate) · Issue #56 · kornelski/http-cache-semantics · GitHub

https://github.com/kornelski/http-cache-semantics/issues/56
generic

http-cache-semantics/index.js at f01112e954b83cfa8765b633ba880e5e980aa54c · kornelski/http-cache-semantics · GitHub

https://github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633ba880e5e980aa54c/index.js#L603-L623
generic

http-cache-semantics/index.js at f01112e954b83cfa8765b633ba880e5e980aa54c · kornelski/http-cache-semantics · GitHub

https://github.com/kornelski/http-cache-semantics/blob/f01112e954b83cfa8765b633ba880e5e980aa54c/index.js#L425-L441
generic

GitHub - kornelski/http-cache-semantics: RFC 7234 in JavaScript. Parses HTTP headers to correctly compute cacheability of responses, even in complex cases · GitHub

https://github.com/kornelski/http-cache-semantics

Vendor Advisories for CVE-2026-93748(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 20:31 UTCEG score recompute
  2. 2026-09-18 20:31 UTCGHSA enrichment
  3. 2026-09-18 20:10 UTCEG score recompute
  4. 2026-09-18 20:10 UTCGHSA enrichment
  5. 2026-09-18 18:27 UTCEG score recompute
  6. 2026-09-18 17:54 UTCEG score recompute
  7. 2026-09-18 17:54 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-93748?
CVE-2026-93748 is a high vulnerability published on September 18, 2026. 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…
When was CVE-2026-93748 disclosed?
CVE-2026-93748 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-93748?
CVE-2026-93748 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-93748?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-93748, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-93748

Explore →

Is Your Infrastructure Affected by CVE-2026-93748?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs