Quick answers
- Is CVE-2026-49364 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-49364 being exploited in the wild.
- How severe is CVE-2026-49364?
- Critical severity, with a CVSS score of 9.1, published 10 September 2026.
- Which products and versions are affected?
- Apache Activemq Artemis 1.0.0 through 2.44.0; Apache Artemis 2.50.0 through 2.56.0.
- Is there a fix for CVE-2026-49364?
- A patch was published on 2026-09-10: Fix available in Artemis 2.57.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-49364 attacked?
- It is attacked over the network or from the adjacent network, in a hosted service.
- Am I affected by CVE-2026-49364?
- Check whether you run Apache Activemq Artemis or Apache Artemis 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.
Technical details
This vulnerability involves credential exposure during the cluster connection handshake in Apache Artemis. An unauthenticated, network-adjacent attacker can intercept cluster discovery traffic to capture administrative credentials in plaintext or weakly protected form during the initial handshake. The attack requires network adjacency but no prior authentication. Successful exploitation grants an attacker administrative access to the Artemis cluster, enabling them to read/modify messages, configure the broker, or disrupt service. The issue affects Artemis 2.50.0–2.56.0 and ActiveMQ Artemis 1.0.0–2.44.0, with a fix available in Artemis 2.57.0.
Affected products
- Apache Artemis 2.50.0 through 2.56.0
- Apache ActiveMQ Artemis 1.0.0 through 2.44.0
Timeline
- 2026-09-10: disclosed: CVE-2026-49364 published
- 2026-09-10: patched: Fix available in Artemis 2.57.0