Is CVE-2026-106123 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-106123 being exploited in the wild.

How severe is CVE-2026-106123?

Medium severity, with a CVSS score of 4, published 6 October 2026.

Which products and versions are affected?

com.rabbitmq:amqp-client (Maven) <= 5.34.0, ECOSYSTEM:introduced=0,fixed=5.35.0; RabbitMQ Java client library prior to 5.35.0.

Is there a fix for CVE-2026-106123?

Yes. com.rabbitmq:amqp-client (Maven): upgrade to 5.35.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-106123 attacked?

It is attacked with local access.

Am I affected by CVE-2026-106123?

Check whether you run com.rabbitmq:amqp-client (Maven) or RabbitMQ Java client library at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-106123: RabbitMQ Java client library credential disclosure in error messages

Q: Is there a fix for CVE-2026-106123?

Yes. com.rabbitmq:amqp-client (Maven): upgrade to 5.35.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-106123 attacked?

It is attacked with local access.

Q: Am I affected by CVE-2026-106123?

Check whether you run com.rabbitmq:amqp-client (Maven) or RabbitMQ Java client library at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-106123 · Severity: medium · CVSS 4 · Published 2026-10-06

The RabbitMQ Java client library is used by applications to connect to RabbitMQ message brokers. When AMQP URI parsing fails, error messages included plaintext usernames and passwords from the connection URI, potentially exposing broker credentials in logs, monitoring systems, and stack traces shared across teams.

Technologies: com.rabbitmq:amqp-client (Maven), RabbitMQ Java client library. Vendors: Maven, RabbitMQ.

Quick answers

Is CVE-2026-106123 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-106123 being exploited in the wild.
How severe is CVE-2026-106123?: Medium severity, with a CVSS score of 4, published 6 October 2026.
Which products and versions are affected?: com.rabbitmq:amqp-client (Maven) <= 5.34.0, ECOSYSTEM:introduced=0,fixed=5.35.0; RabbitMQ Java client library prior to 5.35.0.
Is there a fix for CVE-2026-106123?: Yes. com.rabbitmq:amqp-client (Maven): upgrade to 5.35.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-106123 attacked?: It is attacked with local access.
Am I affected by CVE-2026-106123?: Check whether you run com.rabbitmq:amqp-client (Maven) or RabbitMQ Java client library at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

com.rabbitmq:amqp-client (Maven): upgrade to 5.35.0 or later

# set com.rabbitmq:amqp-client to 5.35.0 in your pom.xml or build.gradle

Technical details

The ConnectionFactoryConfigurator.load() method in versions prior to 5.35.0 includes the raw AMQP URI value in exception messages when parsing fails. Since AMQP URIs commonly contain embedded credentials (amqp://user:password@host), this results in credential disclosure via exception handling. The fix removes unnecessary URI details from error messages.

Affected products

RabbitMQ Java client library prior to 5.35.0

Identifiers

CVE-2026-106123
GHSA-h6w7-qmcm-q6xr

Timeline

2026-10-06: disclosed
2026-08-20: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.