Vulnerability in com.rabbitmq:amqp-client (CVE-2026-69219)
Summary
Vulnerability in com.rabbitmq:amqp-client (CVE-2026-69219). Risk of unauthorized operations or information disclosure. Exploitable via OutOfMemoryError. Mitigation: upgrade to 5.33.1 or later.
Original description
The description as published by the source.
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 uses ValueReader.readBytes to accept a wire-declared contentLength below Integer.MAX_VALUE and allocate a byte array before checking the bytes available in the frame. A malicious AMQP peer can send a LongString or byte-array field with type tag S and a declared length such as 0x7FFFFFFE during the pre-authentication connection.start server-properties table, causing an approximately 2 GB allocation and OutOfMemoryError before readFully consumes data. The resulting memory exhaustion can terminate the JVM and cause denial of service. This issue is fixed in version 5.33.1.
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-69219 has been found in com.rabbitmq:amqp-client.
Attackers can target a specific entry point like OutOfMemoryError 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.1 or later.
If unsure, ask your IT team or search "com.rabbitmq:amqp-client CVE-2026-69219" on the vendor's site.
CVE-2026-69219 (com.rabbitmq:amqp-client) — CWE-789
Attack surface: OutOfMemoryError / TruncatedInputStream / connection.start / contentLength
Patched: 5.33.1 — 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-789) exists in com.rabbitmq:amqp-client. Attackers reach the vulnerable code path via OutOfMemoryError.
Check the vendor advisory for the affected versions of com.rabbitmq:amqp-client. Attack surface: OutOfMemoryError / TruncatedInputStream / connection.start / contentLength.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.33.1.
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.1ステージング環境で 5.33.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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-69219 rabbitmq-java-client
- Ubuntu UBUNTU-CVE-2026-69219 rabbitmq-java-client
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- patch github.com
- patch github.com
- web github.com
- web github.com