CVE-2026-16729

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% (20th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-50416 (ENISA EUVD) · GHSA-v3r7-h72x-cjcm (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 setCookie function does not fully sanitize cookie attributes. 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 domain value is not checked for semicolons and entries in the unparsed array are not sanitized, so attacker-influenced input can inject additional cookie attributes. For example, a domain value containing a semicolon can append attributes such as SameSite, and an unparsed entry can inject attributes such as HttpOnly, without the caller setting them. Applications that pass user-controlled input to these fields, such as multi-tenant or reverse-proxy servers that scope session cookies to a tenant-supplied domain, can have SameSite CSRF protections bypassed, or the Secure, HttpOnly, and SameSite attributes forced, stripped, or overridden. 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.2% × 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
20th
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. 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: 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.

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 5, 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 cookie attribute injection via unsanitized domain and unparsed setCookie fields · Advisory · nodejs/undici · GitHub

https://github.com/nodejs/undici/security/advisories/GHSA-v3r7-h72x-cjcm

Vendor Advisories for CVE-2026-16729(4)

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 / 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

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 9× in last 7d / 46× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 193 refreshes 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 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

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

Frequently asked(5)

What is CVE-2026-16729?
CVE-2026-16729 is a medium-severity vulnerability; its CVE record was published on July 29, 2026. undici's setCookie function does not fully sanitize cookie attributes. 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 domain value is not checked for semicolons and entries in the unparsed array are not sanitized, so attacker-influenced input can…
When was the CVE record for CVE-2026-16729 published?
The CVE record for CVE-2026-16729 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 5, 2026; the record at its source may have been updated since.
Is CVE-2026-16729 actively exploited?
CVE-2026-16729 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-16729?
CVE-2026-16729 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-16729?
A fix for CVE-2026-16729 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-16729 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-16729

Explore →

Is Your Infrastructure Affected by CVE-2026-16729?

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

Book a Demo →Browse All CVEs