Quick answers
- Is CVE-2026-115700 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115700 being exploited in the wild.
- How severe is CVE-2026-115700?
- Informational severity, published 26 October 2026.
- Which products and versions are affected?
- Benoitc Hackney 4.0.1 before 4.9.0.
- Is there a fix for CVE-2026-115700?
- Yes: fixed in hackney 4.9.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115700 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115700?
- Check whether you run Benoitc Hackney at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: hackney 4.9.0
Technical details
An interpretation conflict in hackney_url:normalize/2 and hackney_happy:parse_address/1 allows bypassing IP allowlist validation when a host is percent-encoded (e.g., %5B%3A%3Affff%3A127%2E0%2E0%2E1%5D decodes to [::ffff:127.0.0.1]) or has a trailing dot. The IP-literal gate validates a percent-decoded host but passes it to inet:parse_address/1, which rejects it; however, the connect path strips bracket pairs and the resolver ignores trailing dots, allowing both forms to bypass validation yet still reach the literal address. Exploitation requires network access and an application that follows HTTP redirects or uses user-supplied URLs.
Affected products
- benoitc hackney 4.0.1 before 4.9.0
Timeline
- 2026-10-26: disclosed