CVE-2026-61634: Amqp client RabbitMQ Java Client Accepts Broker Vulnerability

LOW
Advisory Identifier: GHSA-5xwg-cfvj-gff5
Share
CWE-20
Published
Advisory Summary

CVE-2026-61634 is a LOW rabbitmq java client accepts broker vulnerability (CWE-20: Improper Input Validation) affecting Amqp client libraries in the Maven ecosystem. The issue involves rabbitmq java client accepts broker frames larger than the negotiated amqp frame_max. Remediation is available by upgrading affected packages to version 5.33.0.

CVE-2026-61634 at a Glance

CVE Identifier CVE-2026-61634
GHSA Identifier GHSA-5xwg-cfvj-gff5
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-20: Improper Input Validation
Affected Product Amqp client
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-61634

To remediate this vulnerability, upgrade all affected Amqp client dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

com.rabbitmq:amqp-client fixed: 5.33.0 
<dependency>
    <groupId>com.rabbitmq</groupId>
    <artifactId>amqp-client</artifactId>
    <version>5.33.0</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree -Dincludes=com.rabbitmq

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-61634, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=com.rabbitmq

Analyze the terminal output to locate any version of Amqp client in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.33.0), your application is affected.

Note: The mvn dependency:tree -Dincludes=com.rabbitmq command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In Amqp client, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary The max body size was enforced to patch CVE-2023-46120, but even though that limit still works, the frame size itself still exceeds the given max size. ## Root cause The Java client records the AMQP 0-9-1 `frame_max` negotiated during connection tuning, but the socket inbound frame reader continues to validate broker-controlled payload lengths against the much larger `maxInboundMessageBodySize` limit. A broker peer can therefore send a method frame whose payload is larger than the negotiated `frame_max`, have it allocated and decoded, and complete the connection handshake instead of being rejected as a protocol violation. *Reported by Team Atlanta.*

CVE-2026-61634 Affected Amqp client Versions

1 component(s)
Fixed Versions:
5.33.0
Product / Package Ecosystem Affected Versions Fixed Version
com.rabbitmq:amqp-client
maven/com.rabbitmq/amqp-client
Maven
< 5.33.0
5.33.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5xwg-cfvj-gff5
Amqp client Source Repository REPOSITORY
https://github.com/rabbitmq/rabbitmq-java-client/pull/1994
Amqp client Source Repository REPOSITORY
https://github.com/rabbitmq/rabbitmq-java-client/pull/1995
Security Fix Commit FIX COMMIT
https://github.com/rabbitmq/rabbitmq-java-client/commit/08790f09686173eb17b48d08a25edcb32e71a591
Security Fix Commit FIX COMMIT
https://github.com/rabbitmq/rabbitmq-java-client/commit/b491075f42e89967610c40beded68d3680cfd472
Amqp client Source Repository REPOSITORY
https://github.com/rabbitmq/rabbitmq-java-client
Amqp client Release RELEASE
https://github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0

Frequently Asked Questions

What is CVE-2026-61634?
CVE-2026-61634 is a security vulnerability in Amqp client involving RabbitMQ Java client accepts broker frames larger than the negotiated AMQP frame_max under CWE-20: Improper Input Validation.
Which Amqp client versions are affected?
Affected versions include releases prior to 5.33.0 across affected packages: com.rabbitmq:amqp-client.
What version fixes CVE-2026-61634?
Upgrading to 5.33.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is amqp-client affected?
Yes, com.rabbitmq:amqp-client is affected in releases prior to 5.33.0. Upgrade your dependency to 5.33.0 or later.
What CWE is associated with CVE-2026-61634?
CVE-2026-61634 is classified under CWE-20: Improper Input Validation (The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.).
How can I check Maven dependencies for CVE-2026-61634?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=com.rabbitmq'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5xwg-cfvj-gff5",
  "modified" : "2026-08-18T16:36:29Z",
  "published" : "2026-08-18T16:36:29Z",
  "aliases" : [ "CVE-2026-61634" ],
  "summary" : "RabbitMQ Java client accepts broker frames larger than the negotiated AMQP frame_max",
  "details" : "## Summary\nThe max body size was enforced to patch CVE-2023-46120, but even though that limit still works, the frame size itself still exceeds the given max size. \n\n## Root cause\nThe Java client records the AMQP 0-9-1 `frame_max` negotiated during connection tuning, but the socket inbound frame reader continues to validate broker-controlled payload lengths against the much larger `maxInboundMessageBodySize` limit. A broker peer can therefore send a method frame whose payload is larger than the negotiated `frame_max`, have it allocated and decoded, and complete the connection handshake instead of being rejected as a protocol violation.\n\n*Reported by Team Atlanta.*",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "com.rabbitmq:amqp-client"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.33.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5xwg-cfvj-gff5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/rabbitmq-java-client/pull/1994"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/rabbitmq-java-client/pull/1995"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/rabbitmq-java-client/commit/08790f09686173eb17b48d08a25edcb32e71a591"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/rabbitmq-java-client/commit/b491075f42e89967610c40beded68d3680cfd472"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/rabbitmq/rabbitmq-java-client"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-08-18T16:36:29Z",
    "nvd_published_at" : null
  }
}