Apache Software Foundation · Apache ActiveMQ
In Apache ActiveMQ 6.x, the default configuration doesn't secure the API web context (where the Jolokia JMX REST API and the Message REST API are located). It means that anyone can use these layers without any required authentication. Potentially, anyone can interact with the broker (using Jolokia JMX REST API) and/or produce/consume messages or purge/delete destinations (using the Message REST API). To mitigate, users can update the default conf/jetty.xml configuration file to add authentication requirement: <bean id="securityConstraintMapping" class="org.eclipse.jetty.security.ConstraintMapping"> <property name="constraint" ref="securityConstraint" /> <property name="pathSpec" value="/" /> </bean> Or we encourage users to upgrade to Apache ActiveMQ 6.1.2 where the default configuration has been updated with authentication by default.
Public exploit code (PoC-in-GitHub) appeared 24 months after disclosure. No confirmed exploitation is recorded.
6 fixes in apache-activemq over 13 years. The latest fix listed for apache-activemq is 6.2.4.
No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
1 package in 1 ecosystem. Main package: org.apache.activemq:apache-activemq.
Upgrade to 6.2.5 or later
Fixes this CVE and 1 other known vulnerability in this package (CVE-2026-40466).
Set the version to 6.2.5 or later in your pom.xml or build.gradle.
First fixed in 6.1.2 for CVE-2024-32114.
| If you run | Upgrade to |
|---|---|
| 6.0.0 up to 6.1.2 | 6.2.5first fix for this CVE: 6.1.2 |
“Up to” means the second version is the fix and is not affected.
Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.