Skip to content
Threat Brief

← All advisories

CVE-2026-47072

Medium 6.9No known exploitationFix available

CRLF injection in WebSocket upgrade request in hackney

Record last updated

CVSS score

6.9

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.5%

Higher than 46% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in benoitc hackney allows HTTP Request/Response Splitting. The WebSocket upgrade code in src/hackney_ws.erl copies the host, path, headers (ExtraHeaders), and protocols options from the caller-supplied opts map into the internal #ws_data{} record in init/1 and then splices them verbatim into the raw HTTP/1.1 upgrade request by binary concatenation in do_handshake/1. No CRLF or NUL stripping is performed at any of these four injection sites. An attacker who controls any of these options — for example by forwarding URL components or header values from untrusted input into hackney_ws:start_link/1 — can inject arbitrary HTTP headers into the outbound WebSocket upgrade request, leading to header injection, credential spoofing toward the upstream server, log and cache poisoning, or request smuggling via intermediary proxies. This issue affects hackney: from 2.0.0-beta.1 before 4.0.1.

Weakness: CWE-93

Patching and mitigation

Patch status
Fix available (source: NVD (reference tagged Patch))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
benoitchackneyfrom 2.0.0 before 4.0.14.0.1NIST NVD
benoitchackneyfrom 2.0.0-beta.1 before 4.0.14.0.1CVE Program
benoitchackneyfrom 690cecaf236fba49526da404a5bc889a24367a3e before 52310ca807e7b48441ba0e9129171f535313fdd152310ca807e7b48441ba0e9129171f535313fdd1CVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by NVD (reference tagged Patch)

    Source: NVD (reference tagged Patch) (opens in a new tab)

Vendor guidance and references