Skip to main content
CVE-2026-131856VulnerabilityPublished

Pika before 1.5.0 contains an uncontrolled resource allocation vulnerability that allows malicious brokers to exhaust

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131856· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.5.0 when convenient.

Data as of 18 Nov 2026, 02:06 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.9
CNA (VulnCheck)CVSS 3.14.9
Patch
Available – fixed in 1.5.0
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade pika to 1.5.0.

Affected software

ProductAffectedFixed in
pikapikaAffected
  • <1.5.0
Fixed in
  • 1.5.0
PyPIpikapkg:pypi/pikaOther threatsAffected
  • <1.5.0
Fixed in
  • 1.5.0

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 Pika version 1.5.0 and later. Users should upgrade to version 1.5.0 or newer to remediate this vulnerability. No other mitigation guidance is provided or required.

Description

Pika versions prior to 1.5.0 have a vulnerability where malicious brokers can exhaust client memory by declaring oversized frame payloads. Attackers can send frame headers with payload sizes up to 4 GiB, which are not properly checked against the frame_max setting, or send very large message bodies. This can cause consuming applications to terminate unexpectedly due to resource exhaustion.

References

Community reviews

Loading reviews…