Live › vulnerability › CVE-2026-115779
The Effect TypeScript framework's cookie helper writes caller-supplied name, domain and path values into Set-Cookie headers without escaping semicolons. An attacker who controls those values can append attributes such as a broader Domain, SameSite=None or Max-Age, widening a cookie's scope.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 21:19 UTC. All times on this page are UTC.
Only applications that pass attacker-controlled values into makeCookie() for the name, domain or path fields are exposed. Apps that use fixed cookie settings or only encode cookie values are not affected by this flaw.
No product ranges from the sources yet.
@effect/platform and effect in the lockfile.makeCookie() and see whether any name, domain or path argument comes from user input.@effect/platform: move to 0.97.1 or later.effect: move to or later.4.0.0-beta.103Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Effect is a TypeScript framework that consists of several packages that work together to help build TypeScript applications. From @effect/platform 0.1.0 until 0.97.1 and effect 4.0.0-beta.0 until 4.0.0-beta.103, the name, domain, and path fields passed to makeCookie() allow semicolon delimiters that serializeCookie() writes verbatim into Set-Cookie headers. A caller that supplies attacker-controlled values can append cookie attributes, including a broader Domain or, when the caller has not set those options itself, SameSite=None or Max-Age. Encoded cookie values and CR or LF characters remain unaffected. This can widen a cookie's scope or add otherwise-unset cookie attributes. This issue is fixed in @effect/platform 0.97.1 and effect 4.0.0-beta.103.
This page as .md · .json · in your agent: get_signal("CVE-2026-115779")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.