Arbitrary Code Injection Affecting org.apache.activemq:activemq-broker package, versions [,5.19.6)[6.0.0,6.2.5)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Arbitrary Code Injection vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-ORGAPACHEACTIVEMQ-16323117
- published30 Apr 2026
- disclosed24 Apr 2026
- creditFatih Ersinadim, gggggggga
Introduced: 24 Apr 2026
NewCVE-2026-40466 (opens in a new tab)How to fix?
Upgrade org.apache.activemq:activemq-broker to version 5.19.6, 6.2.5 or higher.
Overview
org.apache.activemq:activemq-broker is a high performance Apache 2.0 licensed Message Broker and JMS 1.1 implementation.
Affected versions of this package are vulnerable to Arbitrary Code Injection over the /api/jolokia MBeans interface. A user can execute arbitrary code on the broker's JVM by invoking operations with a malicious discovery URI that feeds into the VM transport's brokerConfig parameter that causes the loading of a remote Spring XML application context using ResourceXmlApplicationContext. This allows for the instantiation of malicious beans through factory methods such as Runtime.exec().
Note:
This is a bypass of the fix for CVE-2026-34197.