GitHub Advisoryadvisory · Hex

GHSA-j9wq-vxxc-94wf Hackney has CR/LF injection in query parameter

MEDIUM Published 2026-06-26 Modified 2026-06-26 Official page ↗
Aliases
CVE-2026-47075
Ecosystem
Hex
Packages
hackney
Severity
Moderate
CVSS vector
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N
Weaknesses
CWE-93
Reviewed
2026-06-26

Affected packages

• Hex hackney: < 4.0.1 → fixed in 4.0.1

Description

Summary `hackney_url:make_url/3` passes the URL query component directly into the HTTP/1.1 request target without percent-encoding `\r` or `\n`. RFC 3986 §3.4 requires characters outside the query grammar to be percent-encoded, but no validation or escaping occurs. An attacker who controls any portion of the URL passed to hackney can inject raw CRLF sequences into the request line, enabling HTTP header injection or full request splitting. Details `hackney_url:make_url/3` in `src/hackney_url.erl` builds the request target by concatenating the path and query binaries. The query string is used as-is — no character-class check, no percent-encoding of `\r` or `\n`. When hackney serializes the request, the query value lands verbatim in the `GET ? HTTP/1.1\r\n` request line. A query value containing `\r\n` terminates the request line early; subsequent bytes are parsed by the server (or any intermediary proxy) as additional header lines or a second request. A concrete example: a URL with query `?q=x HTTP/1.1\r\nX-Injected: yes\r\nX:` produces the following on the wire: ``` GET /?q=x HTTP/1.1 X-Injected: yes X: HTTP/1.1 Host: ... ``` The server sees `X-Injected: yes` as a legitimate request header that the client never intended to send. PoC 1. Listen on a raw TCP port: `nc -lvnp 8080`. 2. Issue: `:hackney.get("http://127.0.0.1:8080/?q=x HTTP/1.1\r\nX-Injected: yes\r\nX:")`. 3. Observe the listener receives `X-Injected: yes` as a standalone header line in the request. Impact HTTP header injection and request splitting against any server hackney connects to. Affects all released versions of hackney before 4.0.1. Exploitation requires an attacker-controlled URL (or URL component) to reach hackney without prior sanitization. Consequences include injecting arbitrary headers (`Authorization`, `Host`, `X-Forwarded-For`) and splitting requests through proxies. CVSS v4.0: 6.8 (MEDIUM). Resources • Introduction commit: https://github.com/benoitc/hackney/commit/8bb1a359a81ae58567c84f8d24564e9742e6f2bd • Patch commit: https://github.com/benoitc/hackney/commit/ca73dd0aba0ed557449c18288bf07241671a43c9

Related

Alias · CVE (1)

  • CVE-2026-47075 Improper Neutralization of CRLF Sequences vulnerability in benoitc hackney allows HTTP Request Splitting. vulnerability

Weakness · CWE (1)

  • CWE-93 Improper Neutralization of CRLF Sequences weakness

References