CVE-2026-47070: benoitc hackney · Open Redirect
Affects benoitc hackneySource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.0 Medium : upgrade to 4.0.1 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.0.1, c58d5b50bade146360b85caf3dc8065807b08246
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 25 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade hackney to 4.0.1; hackney to c58d5b50bade146360b85caf3dc8065807b08246.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| benoitchackney | Affected
| Fixed in
|
| benoitchackney | Affected
| Fixed in
|
Hexhackneypkg:hex/hackneyOther threats | Affected
| Fixed in– |
Hexhackneypkg:hex/hackneyOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:benoitc:hackney:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, users should consider disabling HTTP/3 redirect following or avoid using the vulnerable hackney versions. Monitoring for updates from the benoitc project is recommended to apply any forthcoming patches or official mitigations.
Description
Sensitive Data Exposure vulnerability in benoitc hackney allows Retrieve Embedded Sensitive Data. The HTTP/3 redirect handler in src/hackney_h3.erl passes the original request headers unchanged to the redirect target without performing any cross-origin check. When a client issues an HTTP/3 request with follow_redirect enabled and includes Authorization or Cookie headers, a server responding with a 3xx redirect to a different host will cause the client to forward those credentials verbatim to the new origin. The main hackney.erl module has maybe_strip_auth_on_redirect/2 (guarded by the location_trusted option) to address CVE-2018-1000007, but hackney_h3.erl is missing this protection entirely. This issue affects hackney: from 3.1.1 before 4.0.1.
References
- github.com/benoitc/hackney/security/advisories/GHSA-h73q-4w9q-82h4 (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-47070.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-47070 (opens in a new tab)
- github.com/benoitc/hackney/commit/c58d5b50bade146360b85caf3dc8065807b08246 (opens in a new tab)