CVE-2026-47073
Last modified
CVE-2026-47073 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. Allocation of Resources Without Limits or Throttling vulnerability in benoitc hackney allows Flooding. The WebSocket client in src/hackney_ws.erl imposes no upper bound on memory consumption in three code paths. EPSS estimates a 0.83% chance of exploitation in the next 30 days.
Description
Allocation of Resources Without Limits or Throttling vulnerability in benoitc hackney allows Flooding. The WebSocket client in src/hackney_ws.erl imposes no upper bound on memory consumption in three code paths. First, read_handshake_response/3 accumulates received bytes into a growing buffer with no size cap; the per-receive timeout resets on every chunk, so a server that streams bytes without ever sending \r\n\r\n causes the buffer to grow until memory is exhausted. Second, parse_payload/9 and parse_active_payload/8 do not validate the declared frame payload length against any limit; because RFC 6455 allows payload lengths up to 2^63-1 bytes, a server that announces a very large frame and dribbles bytes causes the accumulation buffer to grow until OOM. Third, the frag_buffer field in #ws_data{} accumulates continuation frames indefinitely; a server that sends an endless stream of non-final (nofin) fragmented frames without ever sending a final (fin) frame grows frag_buffer without bound. In all three cases the attacker only needs to control the WebSocket server the hackney client connects to, with no authentication or special client configuration required. This issue affects hackney: from 2.0.0 before 4.0.1.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS:4.0/AV:N/AC:L/AT:N/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
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Benoitc | Hackney | >= 2.0.0, < 4.0.1 |
References
- https://cna.erlef.org/cves/CVE-2026-47073.htmlPatch, Third Party Advisory
- https://github.com/benoitc/hackney/security/advisories/GHSA-q8jg-fgj4-fphfExploit, Patch, Vendor Advisory
- https://osv.dev/vulnerability/EEF-CVE-2026-47073Patch, Third Party Advisory
- https://github.com/benoitc/hackney/security/advisories/GHSA-q8jg-fgj4-fphfExploit, Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-47073?
How severe is CVE-2026-47073?
How do I fix CVE-2026-47073?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-47068Authorization Bypass Through User-Controlled Key vulnerabili…2.3
- CVE-2026-47069Improper Neutralization of CRLF Sequences ('CRLF Injection')…5.3
- CVE-2026-4707Incorrect boundary conditions in the Graphics: Canvas2D comp…7.5
- CVE-2026-47070Sensitive Data Exposure vulnerability in benoitc hackney all…6.1
- CVE-2026-47071Uncontrolled Resource Consumption vulnerability in benoitc h…7.5
- CVE-2026-47072Improper Neutralization of CRLF Sequences ('CRLF Injection')…7.5
- CVE-2026-47074Improper Certificate Validation vulnerability in ex-aws ex_a…8.7
- CVE-2026-47075Improper Neutralization of CRLF Sequences vulnerability in b…7.5
- CVE-2026-47076Interpretation Conflict vulnerability in benoitc hackney all…6.5
- CVE-2026-47077Allocation of Resources Without Limits or Throttling vulnera…7.5
- CVE-2026-47078Relative Path Traversal vulnerability in Erlang OTP (stdlib …4.8
- CVE-2026-4708Incorrect boundary conditions in the Graphics component. Thi…7.5
Are you affected by CVE-2026-47073?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
