CVE-2026-16728

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% 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
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
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 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(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(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-16728?
CVE-2026-16728 is a medium vulnerability 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 CVE-2026-16728 disclosed?
CVE-2026-16728 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-16728 actively exploited?
CVE-2026-16728 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 92.6% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16728, 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-16728

Explore →

Is Your Infrastructure Affected by CVE-2026-16728?

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

Start Free Scan →Browse All CVEs