@effect/platform
Affected
- introduced
0.1.0, fixed0.97.1(semver)
Fixed versions
0.97.1
Fix
- Fixed version
0.97.1npm install @effect/[email protected]
Advisory
Also known as: CVE-2026-115779
Effect: Cookie attribute injection via domain, path, and name fields in @effect/platform makeCookie()
Impact
The name, domain, and path fields of makeCookie() were validated with a regex that allows ;, the attribute separator in Set-Cookie headers. Because serializeCookie() writes those fields verbatim, a caller who passes untrusted input into any of them can append arbitrary attributes to the header.
For example, a domain of "legit.com; Domain=.parent.tld" serializes to session=token; Domain=legit.com; Domain=.parent.tld. RFC 6265 §5.3 takes the last occurrence, so the injected domain wins and the cookie widens to the parent domain. The same trick sets SameSite=None or Max-Age when the caller has not set those options itself.
The value field is unaffected: it passes through encodeURIComponent, which encodes ;. CR and LF are rejected by the existing regex, so header splitting is not possible.
Patches
Fixed in #6763 (v4) and #6765 (v3): the shared regex is split into per-field validators that reject ;, and serializeCookie() now validates before writing the header.
Workarounds
Do not pass user input into name, domain, or path; set them from application constants.
Medium Basis: The source's own band: MODERATE
0.1.0, fixed 0.97.1 (semver)0.97.1
0.97.1npm install @effect/[email protected]4.0.0-beta.0, fixed 4.0.0-beta.103 (semver)4.0.0-beta.103
4.0.0-beta.103npm 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