CVE-2026-47075: CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection') in benoitc hackney
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 before 4.0.1.
AI Analysis
Technical Summary
The vulnerability CVE-2026-47075 in benoitc hackney (versions before 4.0.1) is due to improper neutralization of CRLF sequences (CWE-93). Specifically, hackney_url:make_url/3 passes the query binary directly without validating or escaping carriage return (\r) and line feed (\n) characters, which must be percent-encoded according to RFC 3986 Section 3.4. This flaw allows an attacker who can control the URL to inject raw CRLF sequences into the HTTP request target, enabling HTTP request splitting and arbitrary HTTP header injection.
Potential Impact
Successful exploitation can allow an attacker to manipulate HTTP requests by injecting arbitrary headers or splitting the request, potentially leading to security issues such as cache poisoning, cross-site scripting, or other HTTP-based attacks. The CVSS 4.0 score is 6.8 (medium severity), reflecting the local attack vector, low attack complexity, partial user interaction, and high impact on integrity and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official patch or fix is indicated, users should monitor the vendor's communications for updates. Until a fix is available, avoid passing untrusted input directly into the URL query component or implement input validation and percent-encoding of CRLF characters before passing URLs to hackney.
CVE-2026-47075: CWE-93 Improper Neutralization of CRLF Sequences ('CRLF Injection') in benoitc hackney
Description
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 before 4.0.1.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-47075 in benoitc hackney (versions before 4.0.1) is due to improper neutralization of CRLF sequences (CWE-93). Specifically, hackney_url:make_url/3 passes the query binary directly without validating or escaping carriage return (\r) and line feed (\n) characters, which must be percent-encoded according to RFC 3986 Section 3.4. This flaw allows an attacker who can control the URL to inject raw CRLF sequences into the HTTP request target, enabling HTTP request splitting and arbitrary HTTP header injection.
Potential Impact
Successful exploitation can allow an attacker to manipulate HTTP requests by injecting arbitrary headers or splitting the request, potentially leading to security issues such as cache poisoning, cross-site scripting, or other HTTP-based attacks. The CVSS 4.0 score is 6.8 (medium severity), reflecting the local attack vector, low attack complexity, partial user interaction, and high impact on integrity and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official patch or fix is indicated, users should monitor the vendor's communications for updates. Until a fix is available, avoid passing untrusted input directly into the URL query component or implement input validation and percent-encoding of CRLF characters before passing URLs to hackney.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-05-18T17:28:08.322Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a149bd3a5ae1af1aad77333
Added to database: 5/25/2026, 6:58:27 PM
Last enriched: 5/25/2026, 6:59:24 PM
Last updated: 5/26/2026, 7:54:32 AM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.