CVE-2026-131856 json
Pika before 1.5.0 Memory Exhaustion via Unbounded AMQP Frame Size
published yesterday modified 15h ago also EUVD-2026-128324 , GHSA-r5q5-528r-x5fv
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository pika/pika. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 6.9
- 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 48%
- public exploits
- 0
- none known
Summary
Pika before 1.5.0 contains an uncontrolled resource allocation vulnerability that allows malicious brokers to exhaust client memory by declaring oversized frame payloads. Attackers can send frame headers declaring up to 4 GiB payloads, unchecked against frame_max, or very large message bodies to terminate consuming applications.
Patch / fix
Is CVE-2026-131856 in your stack? 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
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 15h ago
Exploit prediction
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-18).
Exploits and checks
- github.com https://github.com/pika/pika/security/advisories/GHSA-r5q5-528r-x5fv referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
Inferred packages
No advisory lists a package for this vulnerability yet. The CVE names these as products and links their GitHub repository, and the package registry names the same repository, so they are probably the affected packages. Low confidence: the versions are the CVE’s own for the product, and a stack check reports the package as unchecked when there are none.
| ecosystem | package | repository | affected |
|---|---|---|---|
| pypi | pika | pika/pika | < 1.5.0 |
Affected products
- pika pika
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/pika/pika/commit/115b9b1c920d10da0c497ee9f577ddfa0dc9edb2
patch
-
github.com
/pika/pika/security/advisories/GHSA-r5q5-528r-x5fv
vendor-advisory, exploit, advisory
-
github.com
/pika/pika/releases/tag/1.5.0
release-notes
-
github.com
/pika/pika/blob/1.4.4/pika/frame.py#L195-L226
technical-description
-
vulncheck.com
/advisories/pika-before-1.5.0-memory-exhaustion-via-unbounded-amqp-frame-size
third-party-advisory
Sources
- CVE List CVE-2026-131856
- NVD CVE-2026-131856
- Maintainer advisory GHSA-r5q5-528r-x5fv
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.
The maintainers of pika/pika published their own advisory on GitHub. Reviewed sources take precedence over it.