CVE-2026-16728

MEDIUMNVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (21st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.8 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-50566 (ENISA EUVD) · GHSA-8xcm-r25x-g524 (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

undici's retry interceptor can deliver a response whose body length does not match the Content-Length header exposed to the application after a retry or resume of a partial response. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, a malicious or faulty upstream can return a partial response with a mismatched framing header, close the socket early, and have the retry interceptor assemble a body of a different length while the original Content-Length stays attached. Applications that use the retry interceptor and forward upstream headers and bodies downstream, such as proxies or gateways, may then emit an invalid HTTP response with a stale Content-Length, leading to downstream response desynchronization, connection hangs, or response corruption. Exploitation requires the retry interceptor enabled, an upstream returning a mismatched partial response, and a downstream forwarder that does not remove or recalculate Content-Length. The issue is fixed in undici 6.28.0, 7.29.0, and 8.9.0.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
21st
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 downstream response desynchronization via retry interceptor · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-8xcm-r25x-g524

Vendor Advisories for CVE-2026-16728(3)

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

Patch Availability(5)

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 @ 6.28.0 (fixes < 6.28.0)—ghsa
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—
  • every version up to 6.28.0: fixed in 6.28.0
  • 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(1)

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

Data Freshness Timeline

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

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

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

Frequently asked(5)

What is CVE-2026-16728?
CVE-2026-16728 is a medium-severity vulnerability; its CVE record was published on July 29, 2026. undici's retry interceptor can deliver a response whose body length does not match the Content-Length header exposed to the application after a retry or resume of a partial response. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, a malicious or faulty…
When was the CVE record for CVE-2026-16728 published?
The CVE record for CVE-2026-16728 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-16728 actively exploited?
CVE-2026-16728 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16728?
CVE-2026-16728 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-16728?
A fix for CVE-2026-16728 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-16728 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-16728

Explore →

Is Your Infrastructure Affected by CVE-2026-16728?

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

Book a Demo →Browse All CVEs