Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-106123 medium CVSS 5.5

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

Summary

Vulnerability in com.rabbitmq:amqp-client (CVE-2026-106123). Confidential information can be exposed externally. Exploitable via ConnectionFactory. Mitigation: upgrade to 5.35.0 or later.

Original description

The description as published by the source.

Summary

When property-file/Map-based ConnectionFactory setup fails while parsing the uri key, the library wraps the underlying exception with the raw connection string — including the plaintext username and password — baked verbatim into the new exception's message.

Details

ConnectionFactoryConfigurator.load(ConnectionFactory, Map, String) (src/main/java/com/rabbitmq/client/ConnectionFactoryConfigurator.java, lines 142-155):

String uri = properties.get(prefix + "uri");
if (uri != null) {
    try {
        cf.setUri(uri);
    } catch (URISyntaxException e) {
        throw new IllegalArgumentException("Error while setting AMQP URI: " + uri, e);
    } catch (NoSuchAlgorithmException e) {
        throw new IllegalArgumentException("Error while setting AMQP URI: " + uri, e);
    } catch (KeyManagementException e) {
        throw new IllegalArgumentException("Error while setting AMQP URI: " + uri, e);
    }
}

uri is the full AMQP URI — amqp(s)://username:password@host:port/vhost — concatenated verbatim into the exception message on any of the three catch branches. No masking/redaction exists anywhere in this class or in ConnectionFactory.setUri(). This is the library's documented Spring-Boot/ops-config entry point (ConnectionFactory.load(...), available since 4.4.0), not obscure internal code.

RabbitMQ's own AMQP URI spec (rabbitmq.com/docs/uri-spec) explicitly warns the password "should avoid leaking... th…

Source: NIST National Vulnerability Database 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-106123 has been found in com.rabbitmq:amqp-client.
Attackers can target a specific entry point like ConnectionFactory over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: upgrade com.rabbitmq:amqp-client to 5.35.0 or later.
If unsure, ask your IT team or search "com.rabbitmq:amqp-client CVE-2026-106123" on the vendor's site.

CVE-2026-106123 (com.rabbitmq:amqp-client) — CWE-509 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: ConnectionFactory / uri / KeyManagementException / URISyntaxException
Patched: 5.35.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-509) exists in com.rabbitmq:amqp-client. Attackers reach the vulnerable code path via ConnectionFactory.

📍 Affected scope

Check the vendor advisory for the affected versions of com.rabbitmq:amqp-client. Attack surface: ConnectionFactory / uri / KeyManagementException / URISyntaxException.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 5.35.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.35.0

    ステージング環境で 5.35.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.35.0"}]}]

References

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