CVE-2026-47073
Memory exhaustion DoS in hackney WebSocket client due to unbounded buffers.
Is CVE-2026-47073 being exploited?
Not confirmed. CVE-2026-47073 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.85% probability of exploitation in the next 30 days.
How severe is CVE-2026-47073?
CVE-2026-47073 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47073?
Yes. A fix has been recorded for CVE-2026-47073. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47073 affect?
CVE-2026-47073 affects hackney WebSocket client (Elixir/Erlang). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47073?
Upgrade to hackney 4.0.1+ to remediate
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Client memory exhaustion via large/continuous WebSocket frames; attacker controls server; no auth.
Patch when possible
- affected>= 2.0.0 and < 4.0.1
- affected>= 690cecaf236fba49526da404a5bc889a24367a3e and < ce0109e2970ace6e20ff29bae9d05c3ac22ec6dc
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.