Answer in brief
CVE-2026-47067 records a High severity (CVSS 8.7) vulnerability in Atom table exhaustion via unrecognized URL schemes in hackney. The current sources do not mark it as known exploited. The current feed maps hackney (erlang), benoitc/benoitc/hackney (generic), benoitc/hackney (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 8.7. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps hackney (erlang), benoitc/benoitc/hackney (generic), benoitc/hackney (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| hackneyerlang | >=2.0.0,<4.0.1 | 4.0.1 |
| benoitc/benoitc/hackneygeneric | >=d9713695c0d99855d12c73fd8a0b4be0543950c4 <31f6f0e27e096ad88743dfded4f030a3ee74972e | 31f6f0e27e096ad88743dfded4f030a3ee74972e |
| benoitc/hackneygeneric | >=2.0.0 <4.0.1 | 4.0.1 |
Published upstream
May 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 26, 2026
Allocation of Resources Without Limits or Throttling vulnerability in benoitc hackney allows Flooding. The URL parser in src/hackney_url.erl converts every unrecognized URL scheme to a permanent BEAM atom via binary_to_atom/2. BEAM atoms are never garbage-collected and the atom table defaults to a hard limit of 1,048,576 entries. An attacker who can supply URLs with attacker-chosen scheme prefixes — directly as request targets, as configured webhook URLs, or via Location headers followed during redirects — can exhaust the atom table and crash the entire BEAM VM with system_limit. This issue affects hackney: from 2.0.0 before 4.0.1.
Quoted source text, attributed separately from HOL analysis.