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 21× in last 7d / 59× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 14:25 UTCEG score recompute
  3. 2026-08-20 14:25 UTCVendor advisory
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 12:58 UTCEG score recompute
  6. 2026-08-19 12:58 UTCVendor advisory
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-18 13:03 UTCEG score recompute
  9. 2026-08-18 13:03 UTCVendor advisory
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 12:44 UTCEG score recompute
  12. 2026-08-17 12:44 UTCVendor advisory
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 12:52 UTCEG score recompute
  15. 2026-08-16 12:52 UTCVendor advisory
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 13:00 UTCEG score recompute
  18. 2026-08-15 13:00 UTCVendor advisory
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 13:07 UTCEG score recompute
  21. 2026-08-14 13:07 UTCVendor advisory
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 13:14 UTCEG score recompute
  24. 2026-08-13 13:14 UTCVendor advisory
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 34 more
  1. 2026-08-12 13:22 UTCEG score recompute
  2. 2026-08-12 13:22 UTCVendor advisory
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-11 13:30 UTCEG score recompute
  5. 2026-08-11 13:30 UTCVendor advisory
  6. 2026-08-11 00:00 UTCEPSS rescore
  7. 2026-08-10 13:38 UTCEG score recompute
  8. 2026-08-10 13:38 UTCVendor advisory
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-09 13:45 UTCVendor advisory
  11. 2026-08-08 13:53 UTCEG score recompute
  12. 2026-08-08 13:53 UTCVendor advisory
  13. 2026-08-07 14:00 UTCVendor advisory
  14. 2026-08-06 14:08 UTCEG score recompute
  15. 2026-08-06 14:08 UTCVendor advisory
  16. 2026-08-06 13:46 UTCEPSS rescore
  17. 2026-08-05 19:17 UTCEPSS rescore
  18. 2026-08-05 14:16 UTCEG score recompute
  19. 2026-08-05 14:16 UTCVendor advisory
  20. 2026-08-04 15:10 UTCEPSS rescore
  21. 2026-08-04 14:14 UTCEG score recompute▲ 1.70
  22. 2026-08-04 14:11 UTCNVD updateCVSS v3 → 6.5
  23. 2026-08-04 10:38 UTCEPSS rescore
  24. 2026-08-03 16:29 UTCEG score recompute
  25. 2026-08-03 10:35 UTCEPSS rescore
  26. 2026-08-02 16:37 UTCEG score recompute
  27. 2026-08-02 02:26 UTCEPSS rescore
  28. 2026-08-01 16:45 UTCEG score recompute
  29. 2026-08-01 04:15 UTCEPSS rescore
  30. 2026-07-30 16:34 UTCEG score recompute
  31. 2026-07-30 15:40 UTCEG score recompute
  32. 2026-07-29 21:23 UTCEG score recompute
  33. 2026-07-29 21:07 UTCEG score recompute
  34. 2026-07-29 21:07 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

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