CVE-2026-59980: python-hyper hpack · Uncontrolled Resource Consumption
Affects python-hyper hpackSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.2.0 when convenient.
Data as of 6 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.2.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 23 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade python-hyper hpack to 4.2.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| python-hyperhpack | Affected
| Fixed in
|
PyPIhpackpkg:pypi/hpackOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in python-hyper hpack version 4.2.0, which restricts variable integer decoding to uint32 to prevent run-away computation. Users should upgrade to version 4.2.0 or later. As a temporary workaround, sanitize inputs to the hpack decoder to prevent long sequences of 0xFF bytes that could trigger the vulnerability.
Description
CVE-2026-59980 is a vulnerability in the python-hyper hpack library prior to version 4.2.0. It involves uncontrolled resource consumption due to unbounded variable integer decoding, which can cause quadratic runtime on malformed input. This can effectively block further processing when large unsanitized input is provided. The issue is fixed in version 4.2.0 by restricting variable integer decoding to uint32. A workaround is to sanitize input to the hpack decoder to prevent long sequences of 0xFF values.
References
- github.com/python-hyper/hpack/security/advisories/GHSA-8v8h-hg4w-mvq2 (opens in a new tab)
- github.com/python-hyper/hpack/commit/8cfb02c547740e16dbfe7aba77bad84b297cec2c (opens in a new tab)
- cs.opensource.google/go/x/net/+/master:http2/hpack/hpack.go;l=468;drc=8e2b117aee74f6b86c207a808b0255de45c0a18a (opens in a new tab)
- docs.rs/http2/0.5.19/src/http2/hpack/decoder.rs.html (opens in a new tab)