CVE-2026-14643

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.9 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-03) is not newer than that change (2026-08-04), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-50567 (ENISA EUVD) · GHSA-jr45-8vmc-qm54 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

undici's cache interceptor mishandles optional whitespace placed around the equals sign of a qualified no-cache or private Cache-Control directive. In undici from 7.0.0 up to before 7.29.0 and from 8.0.0 up to before 8.9.0, the parser either drops the directive or stores a field name with literal quote characters, so the cache decision fails to recognize the qualification and the response is stored. In shared-cache mode, this lets a response containing one user's authenticated data be served from cache to a later caller, including an unauthenticated one, when both requests resolve to the same cache key. It affects applications that enable the cache interceptor in shared mode, forward Authorization headers upstream, and receive cacheable responses with qualified directives padded with whitespace around the equals sign. This is the whitespace-around-equals variant that the fix for CVE-2026-9678 did not normalize, and it is fixed in undici 7.29.0 and 8.9.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 29, 2026

Last Modified

August 4, 2026

Advisory Details (2)

Auto-updated Jul 29, 2026
Patch available. Sources: github.
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
GitHub advisoryMentions a patch (unverified)

undici vulnerable to cross-user information disclosure via whitespace around equals in Cache-Control directives · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-jr45-8vmc-qm54

Vendor Advisories for CVE-2026-14643(3)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs24-main-24.18.1-0.1.hum12026-07-30redhat
redhatnodejs26-main-26.5.1-1.5.hum12026-07-29redhat
npmundici @ 7.29.0 (fixes >= 7.0.0, < 7.29.0)—ghsa
npmundici @ 8.9.0 (fixes >= 8.0.0, < 8.9.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (40 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (16 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.5.0+dfsg+~cs3.2.0-3 (14 versions)
  • every version up to 8.9.0+dfsg+~cs3.2.0-1: fixed in 8.9.0+dfsg+~cs3.2.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
undici—
  • 7.0.0 up to 7.29.0: fixed in 7.29.0
  • 8.0.0 up to 8.9.0: fixed in 8.9.0
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 254 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 154 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-11-11 13:35 UTCEchelonGraph re-scored
  4. 2026-11-11 13:35 UTCVendor advisory
  5. 2026-11-11 13:35 UTCGHSA enrichmentGHSA-jr45-8vmc-qm54 · GitHub severity MODERATE · GitHub CVSS 5.9
  6. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  7. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  8. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  9. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  10. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-11-04 00:21 UTCEchelonGraph re-scored
  14. 2026-11-04 00:21 UTCVendor advisory
  15. 2026-11-04 00:21 UTCGHSA enrichmentGHSA-jr45-8vmc-qm54 · GitHub severity MODERATE · GitHub CVSS 5.9
  16. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-11-01 07:58 UTCGHSA enrichmentGHSA-jr45-8vmc-qm54 · GitHub severity MODERATE · GitHub CVSS 5.9
  20. 2026-11-01 07:58 UTCEchelonGraph re-scored
  21. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  22. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 75 more
  1. 2026-10-27 11:07 UTCEchelonGraph re-scored
  2. 2026-10-27 11:07 UTCVendor advisory
  3. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-25 14:48 UTCEchelonGraph re-scored
  6. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  7. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-10-18 05:02 UTCEchelonGraph re-scored
  14. 2026-10-17 18:22 UTCEchelonGraph re-scored
  15. 2026-10-17 18:22 UTCVendor advisory
  16. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  19. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-12 16:33 UTCEchelonGraph re-scored
  23. 2026-10-11 20:10 UTCEchelonGraph re-scored
  24. 2026-10-11 18:22 UTCEchelonGraph re-scored
  25. 2026-10-11 14:56 UTCEchelonGraph re-scored
  26. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  28. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  29. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  30. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  31. 2026-10-06 23:59 UTCEchelonGraph re-scored
  32. 2026-10-06 23:59 UTCVendor advisory
  33. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  34. 2026-10-05 20:50 UTCEchelonGraph re-scored
  35. 2026-10-05 20:50 UTCVendor advisory
  36. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  37. 2026-10-05 00:05 UTCEchelonGraph re-scored
  38. 2026-10-05 00:05 UTCVendor advisory
  39. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  40. 2026-10-04 06:58 UTCEchelonGraph re-scored
  41. 2026-10-04 06:58 UTCVendor advisory
  42. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  43. 2026-10-02 17:56 UTCEchelonGraph re-scored
  44. 2026-10-02 17:56 UTCVendor advisory
  45. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  46. 2026-10-01 03:32 UTCEchelonGraph re-scored
  47. 2026-10-01 03:32 UTCVendor advisory
  48. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  49. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  50. 2026-09-29 07:32 UTCEchelonGraph re-scored
  51. 2026-09-29 07:32 UTCVendor advisory
  52. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  53. 2026-09-28 08:39 UTCVendor advisory
  54. 2026-09-27 19:35 UTCEchelonGraph re-scored
  55. 2026-09-27 19:35 UTCVendor advisory
  56. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  57. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  58. 2026-09-25 05:30 UTCEchelonGraph re-scored
  59. 2026-09-25 05:30 UTCVendor advisory
  60. 2026-09-24 10:56 UTCVendor advisory
  61. 2026-09-23 21:47 UTCEchelonGraph re-scored
  62. 2026-09-23 21:47 UTCVendor advisory
  63. 2026-09-23 05:18 UTCVendor advisory
  64. 2026-09-22 15:45 UTCEchelonGraph re-scored
  65. 2026-09-22 15:45 UTCVendor advisory
  66. 2026-09-20 00:20 UTCEchelonGraph re-scored
  67. 2026-09-20 00:20 UTCVendor advisory
  68. 2026-09-19 04:43 UTCEchelonGraph re-scored
  69. 2026-09-19 04:43 UTCVendor advisory
  70. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  71. 2026-09-18 15:12 UTCVendor advisory
  72. 2026-09-18 01:39 UTCEchelonGraph re-scored
  73. 2026-09-18 01:39 UTCVendor advisory
  74. 2026-09-17 01:34 UTCEchelonGraph re-scored
  75. 2026-09-17 01:34 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-14643?
CVE-2026-14643 is a high-severity vulnerability; its CVE record was published on July 29, 2026. undici's cache interceptor mishandles optional whitespace placed around the equals sign of a qualified no-cache or private Cache-Control directive. In undici from 7.0.0 up to before 7.29.0 and from 8.0.0 up to before 8.9.0, the parser either drops the directive or stores a field name with literal…
When was the CVE record for CVE-2026-14643 published?
The CVE record for CVE-2026-14643 was published on July 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 4, 2026; the record at its source may have been updated since.
Is CVE-2026-14643 actively exploited?
CVE-2026-14643 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14643?
CVE-2026-14643 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-14643?
A fix for CVE-2026-14643 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-14643 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14643

Explore →

Is Your Infrastructure Affected by CVE-2026-14643?

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

Book a Demo →Browse All CVEs