Answer in brief
CVE-2026-47066 records a High severity (CVSS 8.7) vulnerability in Infinite loop in Alt-Svc header parser 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.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:benoitc:hackney:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| hackneyerlang | >=2.0.0,<4.0.1 | 4.0.1 |
| benoitc/benoitc/hackneygeneric | >=408e5fe20302226ea8c74dde2bcbd452d712b5b2 <e548aba1f97ffa3f4750da7b772998fb78c01894 | e548aba1f97ffa3f4750da7b772998fb78c01894 |
| benoitc/hackneygeneric | >=2.0.0-beta.1 <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
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in benoitc hackney allows Excessive Allocation. The Alt-Svc response header parser in src/hackney_altsvc.erl does not guarantee forward progress. When parse_token/2 receives a non-token, non-whitespace, non-comma byte (e.g. !, @, =, ;), it returns the input unchanged. skip_comma/1 also returns the buffer unchanged when the first byte is not a comma. parse_entries/2 then recurses with identical data, creating a tight infinite tail-recursive loop that pins a scheduler at 100% CPU. The calling process never returns. The entry point parse_and_cache/3 is called synchronously in the connection process on every HTTP response. A single-byte Alt-Svc: ! response header is sufficient to trigger the hang; the header is fully controlled by any HTTP origin the client connects to. This issue affects hackney: from 2.0.0-beta.1 before 4.0.1.
Quoted source text, attributed separately from HOL analysis.