← Back
CVE-2026-63335
Vulnerability in com.rabbitmq:amqp-client (CVE-2026-63335)
Summary
vulnerability in com.rabbitmq:amqp-client (CVE-2026-63335). Risk of unauthorized operations or information disclosure. Exploitable via ``UnsupportedOperationException``. Mitigation: upgrade to `5.31.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-63335** has been found in com.rabbitmq:amqp-client.
Attackers can target a specific entry point like ``UnsupportedOperationException`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade com.rabbitmq:amqp-client to **5.31.0** or later.
If unsure, ask your IT team or search "com.rabbitmq:amqp-client CVE-2026-63335" on the vendor's site.
CVE-2026-63335 (com.rabbitmq:amqp-client) — CWE-20 /
Attack surface: `UnsupportedOperationException` / `CommandAssembler` / `SocketFrameHandler.readFrame` / `AMQConnection.MainLoop`
Patched: `5.31.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.
❓ What is the problem
**A vulnerability** (CWE-20) exists in com.rabbitmq:amqp-client. Attackers reach the vulnerable code path via ``UnsupportedOperationException`` without authentication.
📍 Affected scope
com.rabbitmq:amqp-client — . Attack surface: `UnsupportedOperationException` / `CommandAssembler` / `SocketFrameHandler.readFrame` / `AMQConnection.MainLoop`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.31.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'com.rabbitmq:amqp-client' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'com.rabbitmq:amqp-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `com.rabbitmq:amqp-client` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade com.rabbitmq:amqp-client to 5.31.0ステージング環境で 5.31.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
com.rabbitmq:amqp-client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.31.0"}]}]