Skip to main content
VulnerabilityPublished

CVE-2026-69219: rabbitmq-java-client · Excessive Memory Allocation

Affects rabbitmq-java-clientSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.7 High : upgrade to 5.33.1 soon.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.33.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 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 15 Nov 2026.

What to do

Upgrade rabbitmq-java-client and com.rabbitmq/rabbitmq-java-client to 5.33.1.

Affected software

ProductAffectedFixed in
rabbitmqrabbitmq-java-clientAffected
  • <5.33.1
Fixed in
  • 5.33.1
Mavencom.rabbitmq/rabbitmq-java-clientpkg:maven/com.rabbitmq/rabbitmq-java-clientOther threatsAffected
  • <5.33.1
Fixed in
  • 5.33.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade rabbitmq-java-client to version 5.33.1 or later, where this vulnerability is fixed. No other mitigations are specified or recommended by the vendor advisory.

Description

CVE-2026-69219 is a high-severity vulnerability in the rabbitmq-java-client library prior to version 5.33.1. It involves memory allocation with an excessive size value due to improper validation of a declared content length in AMQP frames. A malicious AMQP peer can cause the client to allocate approximately 2 GB of memory, leading to an OutOfMemoryError and denial of service by terminating the JVM. The issue is fixed in version 5.33.1.

References

Community reviews

Loading reviews…