GHSA-g2wm-735q-3f56
Suggest an improvement- Source
- https://github.com/advisories/GHSA-g2wm-735q-3f56
- Import Source
- https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-g2wm-735q-3f56/GHSA-g2wm-735q-3f56.json
- JSON Data
- https://api.osv.dev/v1/vulns/GHSA-g2wm-735q-3f56
- Aliases
-
- CVE-2026-43969
- EEF-CVE-2026-43969
- Published
- 2026-05-11T21:31:34Z
- Modified
- 2026-05-18T18:11:04.197473312Z
- Severity
-
- 2.1 (Low) CVSS_V4 - CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N CVSS Calculator
- Summary
- cowlib: Cookie Request Header Injection via Unvalidated Encoder in cow_cookie:cookie/1
- Details
-
Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in ninenines cowlib allows HTTP request splitting and cookie smuggling via unvalidated cookie name and value fields.
cowcookie:cookie/1 in cowlib builds a client-side Cookie: request header from a list of name-value pairs without validating either field. An attacker who controls the cookie names or values passed to this function can inject ;, ,, CR, LF, or TAB characters into the serialized header. This enables two classes of attack: cookie smuggling within a single header (e.g. injecting "; admin=1" to introduce a phantom cookie that the receiving server treats as authentic) and HTTP request header splitting (injecting CRLF to append arbitrary headers or smuggle a complete second request against a shared upstream proxy). The decoder side (parsecookiename/1, parsecookie_value/1) and setcookie/3 already validate and reject these characters; the encoder alone is missing the check.
This issue affects cowlib from 2.9.0.
- Database specific
{ "nvd_published_at": "2026-05-11T19:16:25Z", "severity": "LOW", "cwe_ids": [ "CWE-93" ], "github_reviewed": true, "github_reviewed_at": "2026-05-18T17:48:35Z" }- References
Affected packages
Hex / cowlib
Package
- Name
- cowlib
- Purl
- pkg:hex/cowlib