CVE-2026-13697

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 74% 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
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

undici's cache interceptor mishandles malformed Cache-Control private directives. In undici 7.0.0 up to before 7.29.0 and 8.0.0 up to before 8.9.0, a response carrying a degenerate qualified private directive, such as private set to an empty value, can be stored in the default shared cache and later served to a different caller with the same cache key, disclosing private response bodies and headers including Set-Cookie. Separately, a Cache-Control header that combines an unqualified private directive with a qualified one triggers an uncaught TypeError in the cache-control parser, which rejects the request and, depending on the consumer's error handling, can terminate the process. Both issues affect applications using the cache interceptor in shared mode, including the default configuration. The issues are fixed in undici 7.29.0 and 8.9.0.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
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 and parse-time crash via degenerate private cache directives · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-4cwx-7wf7-3272

Vendor Advisories for CVE-2026-13697(3)

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

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
undici—8.9.0—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 51× in last 7d / 133× 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 133 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-13697?
CVE-2026-13697 is a critical vulnerability published on July 29, 2026. undici's cache interceptor mishandles malformed Cache-Control private directives. In undici 7.0.0 up to before 7.29.0 and 8.0.0 up to before 8.9.0, a response carrying a degenerate qualified private directive, such as private set to an empty value, can be stored in the default shared cache and…
When was CVE-2026-13697 disclosed?
CVE-2026-13697 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-13697 actively exploited?
CVE-2026-13697 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 74.4% of all scored CVEs.
What is the CVSS score of CVE-2026-13697?
CVE-2026-13697 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-13697?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13697, 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-13697

Explore →

Is Your Infrastructure Affected by CVE-2026-13697?

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

Start Free Scan →Browse All CVEs