CVE-2026-69220: rabbitmq-java-client · Uncontrolled Recursion
Affects rabbitmq-java-clientSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 5.33.1 soon.
Data as of 16 Nov 2026, 20:25 UTC
- 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:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 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 16 Nov 2026.
What to do
Upgrade rabbitmq-java-client and com.rabbitmq/rabbitmq-java-client to 5.33.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rabbitmqrabbitmq-java-client | Affected
| Fixed in
|
Mavencom.rabbitmq/rabbitmq-java-clientpkg:maven/com.rabbitmq/rabbitmq-java-clientOther 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
This vulnerability is fixed in RabbitMQ Java client version 5.33.1. Users should upgrade to version 5.33.1 or later to remediate the issue. No other mitigation or workaround is indicated in the available data.
Description
The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.1, src/main/java/com/rabbitmq/client/impl/ValueReader.java permits ValueReader.readTable and ValueReader.readArray to call ValueReader.readFieldValue recursively for AMQP table type F and AMQP array type A values without a nesting-depth limit. A malicious AMQP server or network intermediary can send approximately 580 nested table levels in the pre-authentication connection.start frame, fitting within the default 131072-byte frame maximum, to trigger StackOverflowError. The error terminates the client input processing thread and causes denial of service. This issue is fixed in version 5.33.1.
References
- github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-93j5-89vc-pph4 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/pull/2007 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/pull/2008 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/commit/09af76fce136f3136931654a0a1d43095c80e2f0 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/commit/db89e34809fbc6ba4e946615f297f3684ccd0acc (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.1 (opens in a new tab)