CVE-2026-115779: Cookie attribute injection via domain, path, and name fields in @effect/platform makeCookie()
Affects @effect/platformSource GCVE Database
Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.97.1 when convenient.
Data as of 10 Nov 2026, 17:36 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 6.3 |
|---|
- Patch
- Available – fixed in 0.97.1, 4.0.0-beta.103
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade @effect/platform to 0.97.1; effect to 4.0.0-beta.103.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@effect/platform | Affected
| Fixed in
|
| npmeffect | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and fixed the vulnerability in versions 0.97.1 and 4.0.0-beta.103. Users should upgrade to these or later versions. As a workaround, avoid passing untrusted user input into the name, domain, or path fields of makeCookie(); instead, use application constants for these values. No other mitigation is required once patched.
Description
A vulnerability in the @effect/platform library's makeCookie() function allows injection of cookie attributes via the name, domain, and path fields. These fields were validated with a regex that permitted the ';' character, enabling attackers to append arbitrary attributes to Set-Cookie headers. This can lead to unintended cookie scope expansion or attribute manipulation. The value field is safe due to encoding, and header splitting is not possible. The issue is fixed in versions 0.97.1 and 4.0.0-beta.103.
References
- github.com/Effect-TS/effect/security/advisories/GHSA-chp3-j5qr-2vfr (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-115779 (opens in a new tab)
- github.com/Effect-TS/effect/pull/6763 (opens in a new tab)
- github.com/Effect-TS/effect/pull/6765 (opens in a new tab)
- github.com/Effect-TS/effect/commit/4a57af24011db1d66e947289d2f7ffc2074696d2 (opens in a new tab)
- github.com/Effect-TS/effect/commit/5859b373b9be04d5037a594196b4743ad80379bd (opens in a new tab)
- github.com/Effect-TS/effect (opens in a new tab)
- github.com/Effect-TS/effect/releases/tag/@effect/platform@0.97.1 (opens in a new tab)
- github.com/Effect-TS/effect/releases/tag/effect@4.0.0-beta.103 (opens in a new tab)