undici
Affected
- introduced
0, fixed6.28.0(semver)
Fixed versions
6.28.0
Fix
- Fixed version
6.28.0npm install [email protected]
Advisory
Also known as: CVE-2026-16729
undici vulnerable to cookie attribute injection via unsanitized domain and unparsed setCookie fields
Impact
The setCookie function has two attribute injection paths. validateCookieDomain does not reject semicolons (validateCookiePath already does at 0x3B), so a domain value like example.com; SameSite=None lands verbatim as Domain=example.com; SameSite=None. The unparsed array's loop only checks each entry contains = and does not sanitize values, so an entry like X-Custom=val; HttpOnly lands unchanged, injecting HttpOnly without the caller setting cookie.httpOnly = true.
Applications that pass user-controlled input to these fields, typically multi-tenant or reverse-proxy servers that scope session cookies to a tenant-supplied domain, can have SameSite CSRF protections bypassed, Secure or HttpOnly forced or stripped, or the intended SameSite tier overridden.
Patches
Patched in undici v6.28.0, v7.29.0, and v8.9.0.
Workarounds
domain values against the RFC 1034 letter-digit-hyphen set before passing to setCookie.unparsed field.Medium Basis: The source's own band: MODERATE
0, fixed 6.28.0 (semver)6.28.0
6.28.0npm install [email protected]7.0.0, fixed 7.29.0 (semver)7.29.0
7.29.0npm install [email protected]8.0.0, fixed 8.9.0 (semver)8.9.0
8.9.0npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0