CVEvulnerability

CVE-2026-47071

8.2 HIGH 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)
8.2 HIGH — CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/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])
7.5 HIGH — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses
CWE-400

Description

Uncontrolled Resource Consumption vulnerability in benoitc hackney allows Flooding. The SOCKS5 transport in src/hackney_socks5.erl correctly applies the caller-supplied timeout to the SOCKS5 negotiation phase, but then upgrades the connection to TLS using the two-argument form ssl:connect/2, which defaults to an infinite timeout. The Timeout value is in scope at the call site but is not forwarded. A hostile SOCKS5 proxy that completes the SOCKS5 handshake normally and then goes silent (or sends a partial TLS ServerHello and stalls) will cause the connecting process to block indefinitely, regardless of the connect_timeout or recv_timeout options supplied by the caller. This issue affects hackney: from 0.10.0 before 4.0.1.

Affected configurations

• benoitc hackney (>= 0.10.0 < 4.0.1)

Related

Weakness · CWE (1)

  • CWE-400 Uncontrolled Resource Consumption weakness

References