CVE-2026-43966
Medium 6.3No known exploitationFix availableHTTP Response Splitting via Non-VCHAR Bytes in cow_http_struct_hd:escape_string/2
Vendor advisory: GHSA-w4f7-4cxr-rv3c
Record last updated
CVSS score
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 18% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') vulnerability in ninenines cowlib allows HTTP response splitting via non-VCHAR bytes in structured-fields string values. cow_http_struct_hd:escape_string/2 in cowlib only escapes \ and ", passing all other bytes through verbatim. This creates an encoder/decoder asymmetry: the matching parser accepts only printable ASCII (0x20–0x7E, excluding " and \), but the encoder emits any byte including CR and LF. An application that builds a structured HTTP header via cow_http_struct_hd:item/1 (or a higher-level wrapper such as cow_http_hd:wt_protocol/1) from attacker-controlled input can have \r\n injected into the serialized header value. Once on the wire, the injected CRLF terminates the current header and any following bytes are interpreted as a new header, enabling HTTP response splitting. This issue affects cowlib: from 2.9.0 before 2.22.0.
Weakness: CWE-113
Patching and mitigation
- Patch status
- Fix available (source: GitHub Advisory Database)
- Fix documented (source date)
- Mitigation
- Validate all values passed into structured-fields header builders (directly via cow_http_struct_hd:item/1 or indirectly via higher-level wrappers) before calling the encoder. Reject any value that is not from a trusted, application-controlled source or that contains CR (\r) or LF (\n) bytes. Applications using cowboy 2.16.0 or later are protected on the server side by the invalid_response_headers option (defaults to error_terminate), which rejects any outgoing response header value containing CR or LF before it reaches the wire. Applications using gun 2.4.0 or later are protected on the client side by the invalid_request_headers request option (defaults to raise), which raises an exception when an outgoing request header value contains CR or LF.
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| erlang | cowboy | all versions before 2.16.0 | 2.16.0 | GitHub Advisory Database |
| erlang | gun | all versions before 2.4.0 | 2.4.0 | GitHub Advisory Database |
| ninenines | cowlib | from 2.9.0 before 2.22.0 | 2.22.0 | CVE Program |
| ninenines | cowlib | from a8b793db3d6ffe91d62f81baf41b1dab4cd78fb6 before 4401b858f2229abb3ea115c60924f6c77e5f8aa3 | 4401b858f2229abb3ea115c60924f6c77e5f8aa3 | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by GitHub Advisory Database
Vendor guidance and references
- cowboy: Add invalid_response_headers HTTP/1 option (opens in a new tab)mitigation
- Fix commit 4401b85 in ninenines/cowlib (opens in a new tab)patch
- gun: Add invalid_request_headers request option (opens in a new tab)mitigation
- EEF CNA record for CVE-2026-43966 (opens in a new tab)related, third-party-advisory
- GitHub Advisory GHSA-w4f7-4cxr-rv3c (opens in a new tab)github-advisory
- Introducing commit a8b793d in ninenines/cowlib (opens in a new tab)related
- OSV record EEF-CVE-2026-43966 (opens in a new tab)related