CVEvulnerability

CVE-2026-47076

6.9 MEDIUM Published 2026-05-25 Modified 2026-07-24 Official page ↗
Status
Analyzed
Published
2026-05-25
Last modified
2026-07-24
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
CVSS 3.1 ([email protected])
6.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Weaknesses
CWE-436, CWE-918

Description

Interpretation Conflict vulnerability in benoitc hackney allows Server Side Request Forgery. hackney_url:normalize/2 URL-decodes the host component after the URL has been parsed into a #hackney_url{} record. OTP's uri_string:parse/1 and inet:parse_address/1 do not decode percent-escapes in the host, so a URL such as http://%31%32%37%2E%30%2E%30%2E%31/ is seen by a caller's allowlist validator with host %31%32%37%2E%30%2E%30%2E%31 (not an IP address), which passes the allowlist check. hackney's normalizer then decodes the host to 127.0.0.1 and opens a TCP connection to loopback. Because hackney:request/5 always calls hackney_url:normalize/2 with no opt-out, every request that takes a binary or list URL is affected. The same technique reaches cloud instance metadata services (169.254.169.254), RFC1918 networks, and any admin interface listening on localhost. This issue affects hackney: from 0.13.0 before 4.0.1.

Affected configurations

• benoitc hackney (>= 0.13.0 < 4.0.1)

Related

Weakness · CWE (2)

  • CWE-436 Interpretation Conflict weakness
  • CWE-918 Server-Side Request Forgery weakness

References