CVE-2026-13697

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.4 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
Trending — Patch released this week

Also known asEUVD-2026-50409 (ENISA EUVD) · GHSA-4cwx-7wf7-3272 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

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.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.5%
EPSS %ILE
40th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 Sep 16, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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
Web page

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html

Vendor Advisories for CVE-2026-13697(9)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatnodejs26-1:26.12.1-3.el10_32026-11-11redhat
redhatnodejs:26-9090020260922082827.rhel92026-11-10redhat
redhatdevspaces/pluginregistry-rhel9:17924952122026-10-26redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17918254692026-10-21redhat
redhatansible-automation-platform/bootc-automation-portal-rhel9:17918656602026-10-13redhat
redhatrhdh/rhdh-hub-rhel9:17913114952026-10-08redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:17912496402026-10-06redhat
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(3)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 71× 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 446 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 346 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-13697?
CVE-2026-13697 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-13697 published?
The CVE record for CVE-2026-13697 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-13697 actively exploited?
CVE-2026-13697 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-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?
A fix for CVE-2026-13697 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-13697 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-13697

Explore →

Is Your Infrastructure Affected by CVE-2026-13697?

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

Book a Demo →Browse All CVEs