Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-47071: Uncontrolled Resource Consumption vulnerability in benoitc hackney allows Flooding

50
This week
HIGH 7.5REMOTEUPGRADE

CVE-2026-47071 is a high-severity flaw (CVSS 7.5) affecting hackney. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • High severity
  • Public exploit reference
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.8% (top 45%)
CISA exploited listNo
WeaknessCWE-400
Published2026-05-25
Last modified2026-07-24
Publisher (CNA): EEF · Vendor: benoitc

Share: LinkedIn · X · Reddit

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

benoitc hackney UPGRADE
Affected: >= 0.10.0 and < 4.0.1
Fixed in: 4.0.1
Safe to downgrade to: a release before 0.10.0
1. Check installed version
apt-cache policy hackney || rpm -q hackney || hackney --version
2. UPGRADE to 4.0.1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade hackney
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade hackney
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.10.0 (Debian / Ubuntu)
apt-cache madison hackney sudo apt install hackney=<VERSION_BEFORE_0.10.0> sudo apt-mark hold hackney
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list hackney sudo dnf downgrade hackney-<VERSION_BEFORE_0.10.0> sudo dnf versionlock add hackney
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-47071?

hackney: upgrade to 4.0.1. Exact commands for each OS are on this page.

Is CVE-2026-47071 being exploited?

CVE-2026-47071 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-47071 affect?

CVE-2026-47071 affects hackney. Severity is high (CVSS 7.5). 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 connecti

How urgent is CVE-2026-47071?

Priority 50/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.