Quick answers
- Is CVE-2026-46605 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-46605 being exploited in the wild.
- How severe is CVE-2026-46605?
- Medium severity, with a CVSS score of 4.3, published 1 June 2026.
- Which products and versions are affected?
- Apache ActiveMQ < 5.19.7, 6.0.0 to < 6.2.6; org.apache.activemq:apache-activemq (Maven) ECOSYSTEM:introduced=0,fixed=5.19.7.
- Is there a fix for CVE-2026-46605?
- Yes. org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-46605 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-46605?
- Check whether you run Apache ActiveMQ or org.apache.activemq:apache-activemq (Maven) 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
- org.apache.activemq:apache-activemq (Maven): upgrade to 5.19.7 or later
# set org.apache.activemq:apache-activemq to 5.19.7 in your pom.xml or build.gradle
Technical details
An improper authorization vulnerability (CWE-285) exists in Apache ActiveMQ's destination removal workflow. The server fails to correctly validate permissions when an authenticated connection attempts to remove existing destinations (queues or topics). A remote attacker with low-privileged credentials can exploit this flaw to delete destinations, leading to a partial loss of availability. The issue is resolved in versions 5.19.7 and 6.2.6.
Affected products
- Apache ActiveMQ Broker < 5.19.7, 6.0.0 to < 6.2.6
- Apache ActiveMQ All < 5.19.7, 6.0.0 to < 6.2.6
- Apache ActiveMQ < 5.19.7, 6.0.0 to < 6.2.6
Identifiers
- CVE-2026-46605
- GHSA-cpw7-g3p5-qrfq
Timeline
- 2026-05-31: disclosed: Initial disclosure on oss-security mailing list
- 2026-06-01: advisory: GitHub and NVD advisories published
- 2026-07-09: other: GitHub advisory reviewed and updated