Vulnerabilities

Vulnerability · CVE-2026-47071

Uncontrolled Resource Consumption vulnerability in benoitc hackney allows Flooding.

Published May 25, 2026 · catalog updated Jul 24, 2026 · Uncontrolled Resource Consumption vulnerability

Check if you run it

No confirmed exploitation is on record for CVE-2026-47071. EPSS is 0.70%. Act only if a listed version of Uncontrolled Resource Consumption vulnerability is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Uncontrolled Resource Consumption vulnerability).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.2
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.70%
Remediation
Advisory link
Affected products
cpe benoitc/hackney

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe benoitc/hackneyversion unspecified

How to fix CVE-2026-47071

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-47071. EPSS is 0.70%. Act only if a listed version of Uncontrolled Resource Consumption vulnerability is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-400: Uncontrolled Resource Consumption. EPSS 0.70%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 25, 2026 · NIST NVD

    Detected

    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.

  2. Jul 24, 2026 · NIST NVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-47071

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-47071

    30-day exploitation probability 0.7%

    first.org
  • NIST NVDVulnerability recordCVE-2026-47071

    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 ss

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.