hackney credential exposure in cross-scheme or port redirects
benoitc hackney
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| benoitc hackney |
| No fix yet |
| benoitc hackney |
| No fix yet |
Original description
Insufficiently Protected Credentials vulnerability in hackney in benoitc hackney allows a redirecting server to obtain the basic_auth and cookie credentials of a request via a same-host redirect to another scheme or port. With follow_redirect enabled, hackney:follow_redirect/10 in src/hackney.erl reissues the request to the Location target after hackney:maybe_strip_auth_on_redirect/3, which compared only the hostname of the current and the redirect URL. A redirect from https to http on the same host resent the Authorization and Cookie headers in cleartext, where an on-path attacker can read them, and a redirect to another port on the same host handed them to a different service. location_trusted forwards credentials to any target by design and is unchanged.
This issue affects hackney: from 2.0.0 before 4.9.0.
From the CVE record · EEF
References
- github.com/benoitc/hackney/releases/tag/4.9.0
- cna.erlef.org/cves/CVE-2026-113440.html
- osv.dev/vulnerability/EEF-CVE-2026-113440
- github.com/benoitc/hackney/pull/979
- github.com/benoitc/hackney/commit/8f944559bdb83da60b5c06f6cf6d842591278364
- github.com/benoitc/hackney/commit/6548384b22ea196023a1963e2967d5715b6d9564Patch
- github.com
- repo.hex.pm
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/113xxx/CVE-2026-113440.json
- nvd.nist.gov/vuln/detail/CVE-2026-113440
- github.com/benoitc/hackney