Skip to main content
VulnerabilityPublished

CVE-2026-61634: rabbitmq-java-client · Improper Input Validation

Affects rabbitmq-java-clientSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 0.0 Medium : upgrade to 5.33.0 when convenient.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
0.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.33.0
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/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 16 Nov 2026.

What to do

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

Affected software

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

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

AI-suggested

Upgrade the rabbitmq-java-client library to version 5.33.0 or later, where this vulnerability is fixed. No other mitigation is indicated or required according to the available information.

Description

CVE-2026-61634 is an improper input validation vulnerability in the RabbitMQ Java client library prior to version 5.33.0. The issue arises because the negotiated AMQP frame_max value is not consistently enforced, allowing a malicious or compromised broker to send oversized method frames. This can cause the client to allocate and decode invalid frames, leading to connection disruption and client-side denial of service. The vulnerability is fixed in version 5.33.0.

References

Community reviews

Loading reviews…