CVEvulnerability
CVE-2026-115700
6.9 MEDIUM
Official page ↗
- Status
- Awaiting Analysis
- Published
- 2026-10-26
- Last modified
- 2026-10-26
- Assigner
- 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- CVSS 4.0 (6b3ad84c-e1a6-4bf7-a703-f496b71e49db)
- 6.9 MEDIUM — CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Weaknesses
- CWE-436, CWE-918
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.
Related
References
- https://cna.erlef.org/cves/CVE-2026-115700.html cna.erlef.org
- https://github.com/benoitc/hackney/commit/452620a92ec1da2e6b4862a049a2a4f04b42068f github.com
- https://github.com/benoitc/hackney/commit/f19561a0b422376348c91537e51377ab7325f4ee github.com
- https://github.com/benoitc/hackney/pull/987 github.com
- https://github.com/benoitc/hackney/releases/tag/4.9.0 github.com
- https://osv.dev/vulnerability/EEF-CVE-2026-115700 osv.dev