Vulnerability in com.rabbitmq:amqp-client (CVE-2026-61634)
Summary
Vulnerability in com.rabbitmq:amqp-client (CVE-2026-61634). Risk of unauthorized operations or information disclosure. Exploitable via frame_max. Mitigation: upgrade to 5.33.0 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61634 has been found in com.rabbitmq:amqp-client.
Attackers can target a specific entry point like frame_max over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade com.rabbitmq:amqp-client to 5.33.0 or later.
If unsure, ask your IT team or search "com.rabbitmq:amqp-client CVE-2026-61634" on the vendor's site.
CVE-2026-61634 (com.rabbitmq:amqp-client) — CWE-20
Attack surface: frame_max / maxInboundMessageBodySize
Patched: 5.33.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in com.rabbitmq:amqp-client. Attackers reach the vulnerable code path via frame_max.
Check the vendor advisory for the affected versions of com.rabbitmq:amqp-client. Attack surface: frame_max / maxInboundMessageBodySize.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.33.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで com.rabbitmq:amqp-client を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade com.rabbitmq:amqp-client to 5.33.0ステージング環境で 5.33.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-61634 rabbitmq-java-client
- Ubuntu UBUNTU-CVE-2026-61634 rabbitmq-java-client