Categories
CVE-2026-63336

Vulnerability in com.rabbitmq:amqp-client (CVE-2026-63336)

Summary

Vulnerability in com.rabbitmq:amqp-client (CVE-2026-63336). Risk of unauthorized operations or information disclosure. Exploitable via TrustEverythingTrustManager. Mitigation: upgrade to 5.33.0 or later.

Original description

The description as published by the source.

Vulnerability Summary

com.rabbitmq.client.TrustEverythingTrustManager accepts ANY TLS certificate (including null chains) and is used as the default trust manager when calling ConnectionFactory.useSslProtocol() without arguments. Combined with hostname verification being disabled by default, this enables trivial man-in-the-middle attacks.

Affected Components

  • com.rabbitmq.client.TrustEverythingTrustManager — accepts any certificate
  • com.rabbitmq.client.ConnectionFactory.useSslProtocol() — uses TrustEverythingTrustManager
  • Hostname verification disabled by default (enableHostnameVerification() must be called explicitly)
  • com.rabbitmq.client.ConnectionFactory.getPassword() — returns plaintext with no redaction
  • Default port 5672 (plaintext) with PLAIN SASL — credentials sent unencrypted

POC (Verified on Java 21, amqp-client 5.25.0)

// TrustEverythingTrustManager accepts ANY certificate including null
TrustEverythingTrustManager tm = new TrustEverythingTrustManager();
tm.checkServerTrusted(null, "RSA");  // No exception — accepts null cert chain
tm.getAcceptedIssuers();  // Returns empty array — trusts all CAs

// ConnectionFactory defaults
ConnectionFactory factory = new ConnectionFactory();
factory.useSslProtocol();  // Uses TrustEverythingTrustManager internally
// enableHostnameVerification() NOT called by default

// Credential exposure
factory.setPassword("secret_password_123");
factory.getPassword();  // Returns "secret_password_123"…

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-63336 has been found in com.rabbitmq:amqp-client.
Attackers can target a specific entry point like TrustEverythingTrustManager 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-63336" on the vendor's site.

CVE-2026-63336 (com.rabbitmq:amqp-client) — CWE-295
Attack surface: TrustEverythingTrustManager
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.

❓ What is the problem

A vulnerability (CWE-295) exists in com.rabbitmq:amqp-client. Attackers reach the vulnerable code path via TrustEverythingTrustManager.

📍 Affected scope

Check the vendor advisory for the affected versions of com.rabbitmq:amqp-client. Attack surface: TrustEverythingTrustManager.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.33.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. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで com.rabbitmq:amqp-client を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch
    Upgrade com.rabbitmq:amqp-client to 5.33.0

    ステージング環境で 5.33.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven com.rabbitmq:amqp-client
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.33.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details