Answer in brief
CVE-2026-47074 records a High severity (CVSS 8.2) vulnerability in Unbounded body accumulation in HTTP/3 response loop in hackney. The current sources do not mark it as known exploited. The current feed maps ex_aws_sns (erlang), hackney (erlang), hackney (erlang), benoitc/benoitc/hackney (generic) and additional mapped packages. 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.2. 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 ex_aws_sns (erlang), hackney (erlang), hackney (erlang), benoitc/benoitc/hackney (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ex_aws_snserlang | >=2.0.1,<2.3.5 | 2.3.5 |
| hackneyerlang | >=4.0.0,<4.0.1 | 4.0.1 |
| hackneyerlang | >=2.0.0,<4.0.1 | 4.0.1 |
| benoitc/benoitc/hackneygeneric | >=0334af206d5099fdf510ed9eda18e34396f065ad <3d25f9fea26c90609de9d64366fedfe5065413bc | 3d25f9fea26c90609de9d64366fedfe5065413bc |
| ex-aws/ex-aws/ex_aws_snsgeneric | >=a7ec21880943f4dac1d59bda557db0ffcd2b61fa <1853d280b152d10384a1e21a22cf22152a60be48 | 1853d280b152d10384a1e21a22cf22152a60be48 |
| ex-aws/ex_aws_snsgeneric | >=2.0.0 <2.3.5 | 2.3.5 |
| 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
Allocation of Resources Without Limits or Throttling vulnerability in benoitc hackney allows Flooding. hackney_h3:await_response_loop/6 accumulates the HTTP/3 response body in memory without any size cap. The after Timeout clause is a per-message inactivity timer that resets on every received chunk, housekeeping message, or settings frame — it is not a wall-clock deadline. A malicious HTTP/3 server that emits one small chunk every Timeout - 1 ms with Fin = false and never sends a final frame keeps the loop alive indefinitely while the accumulation buffer grows linearly without bound, eventually exhausting the BEAM process heap and causing an out-of-memory condition. This issue affects hackney: from 2.0.0-beta.1 before 4.0.1.
Quoted source text, attributed separately from HOL analysis.