CVE Catalog

CVE-2026-47075

HighCVSS 7.5
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.48%

39th percentile - higher than 39% of all known CVEs

Summary

hackney before version 4.0.1 does not percent-encode CR (\r) and LF (\n) characters in the URL query component, enabling HTTP Request Splitting. An attacker controlling the URL can inject raw CRLF sequences into the query string, allowing arbitrary HTTP headers or request splitting.

Risk Assessment

The risk includes HTTP request manipulation, header injection, session hijacking, or cache poisoning attacks, potentially compromising communication integrity.

Recommendation

Upgrade hackney to version 4.0.1 or later, which properly percent-encodes CR and LF characters in URLs.

Other vulnerabilities in hackney

See all
Original NVD description (English source)

Improper Neutralization of CRLF Sequences vulnerability in benoitc hackney allows HTTP Request Splitting. hackney does not percent-encode carriage return (\r) or line feed (\n) characters in the URL query component before constructing the HTTP/1.1 request target. Characters outside the grammar defined in RFC 3986 Section 3.4 must be percent-encoded, but hackney_url:make_url/3 passes the query binary directly without validation or escaping. An attacker who can control all or part of a URL passed to hackney can inject raw CRLF sequences into the query string, which are then sent as HTTP line breaks in the request target. This enables injection of arbitrary HTTP headers or splitting of the HTTP request. This issue affects hackney: from 0.13.1 before 4.0.1.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS