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.
CVE-2026-16729
This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 91% 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).
- Lower severity and no public exploit yet
A fix is available — apply it.
- 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 computedSeverity65% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
July 29, 2026
Last Modified
August 5, 2026
Advisory Details (2)
Auto-updated Jul 29, 2026Security Advisories | OpenJS Foundation CVE Numbering Authority
https://cna.openjsf.org/security-advisories.htmlundici 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-cjcmVendor Advisories for CVE-2026-16729(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- GHSA-v3r7-h72x-cjcmGitHub Security AdvisoriesMedium
undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields
- RHSA-2026:48537Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:48273Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | nodejs24-main-24.18.1-0.1.hum1 | 2026-07-30 | redhat |
| redhat | nodejs26-main-26.5.1-1.5.hum1 | 2026-07-29 | redhat |
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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-undici | 5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (39 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-undici | 7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (15 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-undici | 7.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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| undici | — | 8.9.0 | — |
Weakness Classification(1)
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 18× in last 7d / 69× 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 117 total refreshes for this CVE.
- 2026-09-15 07:50 UTCEG score recompute
- 2026-09-15 07:50 UTCVendor advisory
- 2026-09-14 04:21 UTCEG score recompute
- 2026-09-14 04:21 UTCVendor advisory
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-13 05:04 UTCEG score recompute
- 2026-09-13 05:04 UTCVendor advisory
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-12 05:46 UTCEG score recompute
- 2026-09-12 05:46 UTCVendor advisory
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-11 06:29 UTCEG score recompute
- 2026-09-11 06:29 UTCVendor advisory
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-10 07:12 UTCVendor advisory
- 2026-09-09 07:47 UTCEG score recompute
- 2026-09-09 07:47 UTCVendor advisory
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 20:46 UTCEG score recompute
- 2026-09-07 20:46 UTCVendor advisory
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-06 10:48 UTCEG score recompute
- 2026-09-06 10:48 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-05 11:30 UTCEG score recompute
- 2026-09-05 11:30 UTCVendor advisory
- 2026-09-04 11:55 UTCEG score recompute
- 2026-09-04 11:55 UTCVendor advisory
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 23:13 UTCEG score recompute
- 2026-09-01 23:13 UTCVendor advisory
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-31 23:55 UTCVendor advisory
- 2026-08-30 22:34 UTCEG score recompute
- 2026-08-30 22:34 UTCVendor advisory
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 23:17 UTCEG score recompute
- 2026-08-29 23:17 UTCVendor advisory
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 23:45 UTCVendor advisory
- 2026-08-27 00:17 UTCEG score recompute
- 2026-08-27 00:17 UTCVendor advisory
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 00:59 UTCEG score recompute
- 2026-08-26 00:59 UTCVendor advisory
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 01:42 UTCEG score recompute
- 2026-08-25 01:42 UTCVendor advisory
- 2026-08-24 02:25 UTCVendor advisory
- 2026-08-23 02:42 UTCVendor advisory
- 2026-08-22 03:25 UTCEG score recompute
- 2026-08-22 03:25 UTCVendor advisory
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 04:07 UTCEG score recompute
- 2026-08-21 04:07 UTCVendor advisory
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 04:50 UTCEG score recompute
- 2026-08-20 04:50 UTCVendor advisory
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 05:33 UTCVendor advisory
- 2026-08-18 06:15 UTCEG score recompute
- 2026-08-18 06:15 UTCVendor advisory
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 06:58 UTCEG score recompute
- 2026-08-17 06:58 UTCVendor advisory
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 07:41 UTCEG score recompute
- 2026-08-16 07:41 UTCVendor advisory
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 08:24 UTCEG score recompute
- 2026-08-15 08:24 UTCVendor advisory
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 09:06 UTCVendor advisory
- 2026-08-13 09:49 UTCEG score recompute
- 2026-08-13 09:49 UTCVendor advisory
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 10:32 UTCEG score recompute
- 2026-08-12 10:32 UTCVendor advisory
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 11:14 UTCEG score recompute
- 2026-08-11 11:14 UTCVendor advisory
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 11:57 UTCEG score recompute
- 2026-08-10 11:57 UTCVendor advisory
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 12:40 UTCEG score recompute
- 2026-08-09 12:40 UTCVendor advisory
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 13:23 UTCEG score recompute
- 2026-08-08 13:23 UTCVendor advisory
- 2026-08-07 14:05 UTCVendor advisory
- 2026-08-06 14:48 UTCEG score recompute
- 2026-08-06 14:48 UTCVendor advisory
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 15:31 UTCEG score recompute▲ 1.70
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
- CVE-2001-0825EG 10.0HIGH
- CVE-2001-0554EG 10.0EPSS p98HIGH
- CVE-2001-0414EG 10.0EPSS p100HIGH
- CVE-2001-0191EG 10.0EPSS p92HIGH
- CVE-2001-0301EG 10.0EPSS p91HIGH
- CVE-2001-0197EG 10.0EPSS p96HIGH
- CVE-2001-0233EG 10.0EPSS p96HIGH
- CVE-2001-0010EG 10.0EPSS p98HIGH
- CVE-2001-0011EG 10.0EPSS p94HIGH
- CVE-2001-0013EG 10.0EPSS p96HIGH
Same CWE
10 shownCWE-74
- CVE-2014-8423EG 10.0EPSS p99HIGH
- CVE-2015-10062NVD 5.5EG 9.8CRITICAL
- CVE-2015-10027NVD 5.5EG 9.8CRITICAL
- CVE-2016-15007NVD 5.5EG 9.8CRITICAL
- CVE-2016-15004NVD 7.3EG 9.8CRITICAL
- CVE-2013-4144EG 9.8CRITICAL
- CVE-2013-7487EG 9.8CRITICAL
- CVE-2014-4678EG 9.8EPSS p92CRITICAL
- CVE-2014-4967EG 9.8CRITICAL
- CVE-2014-4966EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-16729?
When was CVE-2026-16729 disclosed?
Is CVE-2026-16729 actively exploited?
What is the CVSS score of CVE-2026-16729?
How do I remediate CVE-2026-16729?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-16729
Is Your Infrastructure Affected by CVE-2026-16729?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.