CVE-2026-49364: Apache Artemis, Apache ActiveMQ Artemis: Pre-Authentication Cluster Credential Exposure to Discovered Peers
Apache Artemis CVE-2026-49364 exposes cluster credentials to network-adjacent peers discovered before authentication completes.
Apache disclosed a pre-authentication credential exposure issue in Apache Artemis and Apache ActiveMQ Artemis, tracked as CVE-2026-49364. Affected components span artemis-core-client and artemis-server from version 1.0.0 (ActiveMQ Artemis) and 2.50.0 (Artemis) through 2.44.0 and 2.56.0 respectively. An unauthenticated network-adjacent attacker can leverage credentials exposed to discovered cluster peers. Apache rates the issue as important.
- Cluster credentials are exposed to discovered peers pre-authentication
- Network-adjacent unauthenticated attacker can leverage exposed credentials
- Very broad affected range: ActiveMQ Artemis 1.0.0-2.44.0 and Artemis 2.50.0-2.56.0
- Rated important by the Apache Security Team
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-49364 | Pre-Auth Cluster Credential Exposure in Apache ActiveMQ Artemis Discovery Apache ActiveMQ Artemis brokers do not enforce authentication for the initial cluster connection handshake (CWE-306, Missing Authentication for Critical Function), so cluster administrative credentials are exchanged without authentication during discovery-driven cluster connections. An unauthenticated, network-adjacent attacker positioned on the same network segment as the brokers can capture these cluster administrative credentials during the handshake. With those credentials, the attacker can gain administrative access to the messaging cluster, compromising broker administration and message flows. Only deployments running affected versions in a clustered configuration that relies on discovery are exposed; this requires the attacker to already have access to the broker network, so internet exposure alone is not the primary risk. No exploitation has been reported, no public proof-of-concept exists, the issue is not in CISA's KEV, and CVSS scoring is pending; version 2.57.0 fixes the flaw. Do: Upgrade all cluster nodes to version 2.57.0, which fixes the issue. Until patched, restrict broker cluster/discovery network traffic to a trusted, isolated network segment (e.g., a dedicated VLAN) and rotate cluster administrative credentials if unauthenticated peers may have joined discovery. Also review broker logs for unexpected discovery or handshake connections from unknown hosts. | 9.1 | <1% |
| large≈10,000–100,000 clustered broker deployments (est.) |
Posted by Clebert Suconic on Sep 09 Severity: important Affected versions: - Apache Artemis (org.apache.artemis:artemis-core-client) 2.50.0 through 2.56.0 - Apache Artemis (org.apache.artemis:artemis-server) 2.50.0 through 2.56.0 - Apache ActiveMQ Artemis (org.apache.activemq:artemis-core-client) 1.0.0 through 2.44.0 - Apache ActiveMQ Artemis (org.apache.activemq:artemis-server) 1.0.0 through 2.44.0 Description: An unauthenticated network-adjacent attacker can leverage...
This source does not provide full text. Read it at seclists.org.