Live › vulnerability › CVE-2026-115700
Go to dashboardhackney, an Erlang HTTP client, connects to IP addresses written in forms that an application's allowlist does not recognize, such as a percent-encoded bracketed IPv6 literal or an IPv4 address with a trailing dot. An attacker who can supply a URL or a redirect target can therefore reach internal addresses such as 127.0.0.1 and make server-side requests there.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 14:30 UTC. All times on this page are UTC.
Applications that use hackney 4.0.1 before 4.9.0 to fetch URLs supplied or influenced by users, and that rely on a string or parse-based allowlist of IP addresses to block internal targets. Applications that only connect to fixed hosts, use domain names without a trailing dot, or use unencoded IPv6 literals are not affected by the trailing-dot and encoded-bracket forms described here.
No product ranges from the sources yet.
hackney versions from 4.0.1 up to but not including 4.9.0uri_string:parse/1 or inet:parse_address/1 used as an SSRF allowlist on URLs passed to hackney4.9.0 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-115700")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.