CVE-2026-97200 json
Unbounded response body buffering and decompression in hackney
published 16d ago modified 16d ago also EEF-CVE-2026-97200 , EUVD-2026-109837
- cvss
- 8.2
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
Allocation of Resources Without Limits or Throttling vulnerability in hackney_conn in benoitc hackney allows a malicious HTTP server to exhaust client memory via an oversized or highly compressed response body. hackney:request/5 and hackney:body/1 return the whole response body, and nothing bounds how much the connection process buffers. Any server the client requests can trigger it.
hackney_conn:read_full_body/2 and the HTTP/2 and HTTP/3 accumulators append every chunk until the body ends. With {auto_decompress, true} the buffered body is then inflated in one step with zlib:gunzip/1 or zlib:inflate/2, which return the whole output at once.
This issue affects hackney: from 2.0.0-beta.1 before 4.9.0.
Patch / fix
- hex hackney 4.9.0
- benoitc hackney 4.9.0
- github.com/benoitc/hackney@dc41b79 commit
- github.com/benoitc/hackney@493e8bf commit
- github.com/benoitc/hackney#980 pull request
- github.com/benoitc/hackney/releases/tag/4.9.0 release
Is CVE-2026-97200 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 16d ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:L/AT:P/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 |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | hackney | >=2.0.0-beta.1, <4.9.0 |
4.9.0 |
Affected products
- benoitc hackney
Classification
References
-
github.com
/benoitc/hackney/pull/980
related, web
-
github.com
/benoitc/hackney/commit/dc41b79339ca0c41e16d3f2dd17172bc2de855d6
related, web
-
github.com
/benoitc/hackney/commit/493e8bf83a391548e5101792276ab3fc428fa76c
patch
-
github.com
/benoitc/hackney/releases/tag/4.9.0
vendor-advisory, related, advisory
-
cna.erlef.org
/cves/CVE-2026-97200.html
related, web
-
osv.dev
/vulnerability/EEF-CVE-2026-97200
related
-
hex.pm
/packages/hackney
package
Sources
- CVE List CVE-2026-97200
- NVD CVE-2026-97200
- OSV EEF-CVE-2026-97200
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.