CVE-2026-14643

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
34(Track)
EG Risk 34/100SSVC: Track

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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

July 29, 2026

Last Modified

August 4, 2026

Advisory Details (2)

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

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
github Patch Available

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs24-main-24.18.1-0.1.hum12026-07-30redhat
redhatnodejs26-main-26.5.1-1.5.hum12026-07-29redhat

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 rangeFixed inDependents
node-undici5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (39 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (15 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.5.0+dfsg+~cs3.2.0-3 (14 versions)8.9.0+dfsg+~cs3.2.0-1
npm(1)
PackageVulnerable rangeFixed inDependents
undici8.9.0

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 90× 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.

Showing the most recent 100 of 162 total refreshes for this CVE.

  1. 2026-09-19 04:43 UTCEG score recompute
  2. 2026-09-19 04:43 UTCVendor advisory
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 15:12 UTCVendor advisory
  5. 2026-09-18 01:39 UTCEG score recompute
  6. 2026-09-18 01:39 UTCVendor advisory
  7. 2026-09-17 01:34 UTCEG score recompute
  8. 2026-09-17 01:34 UTCVendor advisory
  9. 2026-09-16 14:07 UTCEPSS rescore
  10. 2026-09-16 05:47 UTCEG score recompute
  11. 2026-09-16 05:47 UTCVendor advisory
  12. 2026-09-16 05:14 UTCEPSS rescore
  13. 2026-09-15 07:45 UTCEG score recompute
  14. 2026-09-15 07:45 UTCVendor advisory
  15. 2026-09-14 04:23 UTCEG score recompute
  16. 2026-09-14 04:23 UTCVendor advisory
  17. 2026-09-13 16:46 UTCEPSS rescore
  18. 2026-09-13 15:19 UTCVendor advisory
  19. 2026-09-13 01:36 UTCEG score recompute
  20. 2026-09-13 01:36 UTCVendor advisory
  21. 2026-09-12 15:00 UTCEPSS rescore
  22. 2026-09-12 12:28 UTCVendor advisory
  23. 2026-09-11 22:02 UTCEG score recompute
  24. 2026-09-11 22:02 UTCVendor advisory
  25. 2026-09-11 14:52 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:36 UTCEPSS rescore
  2. 2026-09-11 08:53 UTCVendor advisory
  3. 2026-09-10 19:48 UTCEG score recompute
  4. 2026-09-10 19:48 UTCVendor advisory
  5. 2026-09-10 09:34 UTCEPSS rescore
  6. 2026-09-10 04:29 UTCVendor advisory
  7. 2026-09-09 07:42 UTCEG score recompute
  8. 2026-09-09 07:42 UTCVendor advisory
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 20:36 UTCEG score recompute
  11. 2026-09-07 20:36 UTCVendor advisory
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 22:31 UTCEG score recompute
  14. 2026-09-06 22:31 UTCVendor advisory
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-06 08:07 UTCVendor advisory
  17. 2026-09-05 19:02 UTCEG score recompute
  18. 2026-09-05 19:02 UTCVendor advisory
  19. 2026-09-05 05:09 UTCEG score recompute
  20. 2026-09-05 05:08 UTCVendor advisory
  21. 2026-09-04 11:52 UTCEG score recompute
  22. 2026-09-04 11:52 UTCVendor advisory
  23. 2026-09-04 05:06 UTCEPSS rescore
  24. 2026-09-02 14:11 UTCEPSS rescore
  25. 2026-09-01 22:45 UTCEG score recompute
  26. 2026-09-01 22:45 UTCVendor advisory
  27. 2026-09-01 13:53 UTCEPSS rescore
  28. 2026-09-01 04:39 UTCEPSS rescore
  29. 2026-08-31 23:52 UTCVendor advisory
  30. 2026-08-31 01:15 UTCEG score recompute
  31. 2026-08-31 01:15 UTCVendor advisory
  32. 2026-08-30 19:17 UTCEPSS rescore
  33. 2026-08-30 12:10 UTCEG score recompute
  34. 2026-08-30 12:10 UTCVendor advisory
  35. 2026-08-30 01:22 UTCEPSS rescore
  36. 2026-08-29 23:04 UTCEG score recompute
  37. 2026-08-29 23:04 UTCVendor advisory
  38. 2026-08-28 21:41 UTCEPSS rescore
  39. 2026-08-27 20:54 UTCEG score recompute
  40. 2026-08-27 20:54 UTCVendor advisory
  41. 2026-08-27 14:25 UTCEPSS rescore
  42. 2026-08-27 03:26 UTCEG score recompute
  43. 2026-08-27 03:26 UTCVendor advisory
  44. 2026-08-26 14:46 UTCEPSS rescore
  45. 2026-08-26 14:19 UTCVendor advisory
  46. 2026-08-26 01:13 UTCEG score recompute
  47. 2026-08-26 01:13 UTCVendor advisory
  48. 2026-08-25 13:48 UTCEPSS rescore
  49. 2026-08-25 12:08 UTCVendor advisory
  50. 2026-08-24 23:03 UTCEG score recompute
  51. 2026-08-24 23:03 UTCVendor advisory
  52. 2026-08-24 09:59 UTCEG score recompute
  53. 2026-08-24 09:59 UTCVendor advisory
  54. 2026-08-23 20:54 UTCVendor advisory
  55. 2026-08-23 07:49 UTCEG score recompute
  56. 2026-08-23 07:49 UTCVendor advisory
  57. 2026-08-23 00:19 UTCEPSS rescore
  58. 2026-08-22 18:45 UTCVendor advisory
  59. 2026-08-22 05:40 UTCEG score recompute
  60. 2026-08-22 05:40 UTCVendor advisory
  61. 2026-08-21 23:49 UTCEPSS rescore
  62. 2026-08-21 16:35 UTCVendor advisory
  63. 2026-08-21 03:30 UTCEG score recompute
  64. 2026-08-21 03:30 UTCVendor advisory
  65. 2026-08-20 22:55 UTCEPSS rescore
  66. 2026-08-20 14:25 UTCVendor advisory
  67. 2026-08-20 00:25 UTCEG score recompute
  68. 2026-08-20 00:25 UTCVendor advisory
  69. 2026-08-19 17:03 UTCEPSS rescore
  70. 2026-08-19 11:20 UTCVendor advisory
  71. 2026-08-18 22:15 UTCEG score recompute
  72. 2026-08-18 22:15 UTCVendor advisory
  73. 2026-08-18 13:48 UTCEPSS rescore
  74. 2026-08-18 09:03 UTCVendor advisory
  75. 2026-08-17 19:53 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-14643?
CVE-2026-14643 is a high vulnerability 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 CVE-2026-14643 disclosed?
CVE-2026-14643 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14643 actively exploited?
CVE-2026-14643 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 76.7% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14643, 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

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.