What’s Vulnerable › Vulnerabilities
CVE-2026-115700: SSRF allowlist bypass via percent-encoded bracketed IPv6 or trailing-dot IP literal in hackney
- Severity: medium (CVSS 6.9 v4.0)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.1% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-10-26 · updated 2026-10-26
- Weakness: CWE-436
Description
Interpretation Conflict vulnerability in hackney_url in benoitc hackney allows Server Side Request Forgery via a percent-encoded bracketed IPv6 literal or an IP literal with a trailing dot. A host such as %5B%3A%3Affff%3A127%2E0%2E0%2E1%5D (decoding to [::ffff:127.0.0.1]) or 127.0.0.1. is not an IP address to a caller's allowlist built on uri_string:parse/1 and inet:parse_address/1, while hackney connects to the address it denotes. The same applies to a Location target when redirects are followed. The IP-literal gate that hackney_url:normalize/2 applies to a percent-decoded host, added to close the percent-encoded IP bypass of CVE-2026-47076, passes the decoded value to inet_parse:address/1 as is. The connect path in hackney_happy:parse_address/1 drops a surrounding bracket pair, and the resolver ignores a trailing dot, so both forms pass the gate and still reach the literal address. Domain names with a trailing dot and unencoded IPv6 literals are not affected. This issue affects hackney: from 4.0.1 before 4.9.0.
Affected products
- benoitc hackney: from 4.0.1 before 4.9.0 — fixed in 4.9.0
How to fix
Upgrade to a fixed version: benoitc hackney 4.9.0. Check the vendor advisory for mitigations.
References
- https://cna.erlef.org/cves/CVE-2026-115700.html
- https://github.com/benoitc/hackney/commit/452620a92ec1da2e6b4862a049a2a4f04b42068f
- https://github.com/benoitc/hackney/commit/f19561a0b422376348c91537e51377ab7325f4ee
- https://github.com/benoitc/hackney/pull/987
- https://github.com/benoitc/hackney/releases/tag/4.9.0
- https://osv.dev/vulnerability/EEF-CVE-2026-115700
Get alerted when CVE-2026-115700 or the next vulnerability affects your stack