Security readout for executives and security teams
Plain-English summary
Hackney can place unescaped carriage-return or line-feed characters from a URL query into an HTTP/1.1 request. If an attacker influences that URL, they may inject headers or split the request, potentially compromising downstream request integrity. The issue affects versions 0.13.1 through 4.0.0.
Executive priority
Prioritize remediation for internet-facing or multi-tenant applications where users influence outbound URLs. The moderate rating supports prompt, risk-based patching rather than emergency response absent exploitation evidence. Escalate if affected hackney paths reach sensitive upstream services, authentication boundaries, proxies, or systems that trust injected headers.
Technical view
hackney_url:make_url/3 passes query binaries into the HTTP/1.1 request target without validating or percent-encoding CR/LF characters as required by RFC 3986. This creates CWE-93 HTTP request-splitting exposure. The supplied CVSS 4.0 score is 6.8, with integrity impact dependent on attacker-controlled URL input and additional interaction or preconditions.
Likely exposure
Exposure is most likely where applications use hackney 0.13.1 through 4.0.0 and allow untrusted data to influence complete URLs or query components. Systems constructing only trusted URLs, or independently rejecting or encoding CR/LF characters, have lower practical exposure. Transitive dependencies may conceal affected installations.
Exploitation context
The source bundle does not establish active exploitation, and the CVE is not listed as KEV. Exploitation requires attacker influence over all or part of a URL passed to hackney. The supplied vector also indicates local access, additional preconditions, and user interaction, so reachability depends heavily on application data flow.
Researcher notes
The vulnerable range is 0.13.1 before 4.0.1, with a referenced corrective commit. Confirm actual reachability at hackney_url:make_url/3 and whether the resulting request uses HTTP/1.1. The bundle establishes possible header injection and request splitting, but provides no evidence of observed exploitation or universal exploitability across applications.
Mitigation direction
- Upgrade hackney to version 4.0.1 or later.
- Identify and update applications carrying affected hackney versions transitively.
- Reject or safely encode CR/LF characters in untrusted URL and query inputs.
- Review the vendor advisory before relying on compensating controls.
Validation and detection
- Inventory direct and transitive hackney versions across deployed applications.
- Trace whether untrusted input can influence URLs or query components passed to hackney.
- Confirm URL controls reject or percent-encode carriage returns and line feeds.
- Verify deployed builds resolve hackney to version 4.0.1 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-93: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-47075 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——EEFVulnerability scoring details
Base CVSS 4.0 score
6.8MediumVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/benoitc/hackney/security/advisories/GHSA-j9wq-vxxc-94wfCVE reference, EEF · vendor-advisory, related
- https://cna.erlef.org/cves/CVE-2026-47075.htmlCVE reference, EEF · related
- https://osv.dev/vulnerability/EEF-CVE-2026-47075CVE reference, EEF · related
- https://github.com/benoitc/hackney/commit/ca73dd0aba0ed557449c18288bf07241671a43c9CVE reference, EEF · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of CRLF Sequences ('CRLF Injection')
Improper Neutralization of CRLF Sequences ('CRLF Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.