CVE-2026-47075
HIGHDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 39% of all known CVEs.
References
Related Vulnerabilities
Other CWE-93 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-61884 | High | 7.5 | 98% | KEV + Ransom | - |
| CVE-2022-0666 | High | 7.5 | 44% | - | Fix |
| CVE-2016-3115 | Medium | 6.4 | 37% | - | Fix |
| CVE-2024-20337 | High | 8.2 | 30% | - | Fix |
| CVE-2021-39172 | High | 8.8 | 29% | - | Fix |
| CVE-2016-4975 | Medium | 6.1 | 20% | - | Fix |
Common questions
How do I fix CVE-2026-47075?
Upgrade hackney to 4.0.1 or later.
Is CVE-2026-47075 being actively exploited?
Not that we know of. CVE-2026-47075 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.48% is the estimated probability that it will be exploited in the next 30 days. That is higher than 39% of all scored CVEs.
How severe is CVE-2026-47075?
CVE-2026-47075 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-47075 affect?
Published advisories record a fix for hackney (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-47075
Markdown
[](https://tridentstack.com/cve/CVE-2026-47075)HTML
<a href="https://tridentstack.com/cve/CVE-2026-47075"><img src="https://tridentstack.com/cve/badge/CVE-2026-47075.svg" alt="CVE-2026-47075"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-07-24.