Improper Input Validation Affecting apache-activemq-6.2 package, versions <6.2.8-r0
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 applications- Snyk IDSNYK-MINIMOSLATEST-APACHEACTIVEMQ62-18312808
- published26 Jul 2026
- disclosed1 Jun 2026
Introduced: 1 Jun 2026
CVE-2026-42588 (opens in a new tab)How to fix?
Upgrade Minimos:latest apache-activemq-6.2 to version 6.2.8-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream apache-activemq-6.2 package and not the apache-activemq-6.2 package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ.
Apache ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console. The default Jolokia access policy permits exec operations on all ActiveMQ MBeans (org.apache.activemq:*), including BrokerService.addNetworkConnector(String).
An authenticated attacker can invoke these operations with a crafted discovery URI that triggers the VM transport's brokerConfig parameter using the "masterslave:// " URL which can allow loading a Spring XML application context using ResourceXmlApplicationContext. Because Spring's ResourceXmlApplicationContext instantiates all singleton beans before the BrokerService validates the configuration, arbitrary code execution occurs on the broker's JVM through bean factory methods such as Runtime.exec(). This issue affects Apache ActiveMQ Broker: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ All: before 5.19.7, from 6.0.0 before 6.2.6; Apache ActiveMQ: before 5.19.7, from 6.0.0 before 6.2.6.
Users are recommended to upgrade to version 5.19.7 or 6.2.6, which fixes the issue.
References
- https://www.cve.org/CVERecord?id=CVE-2026-42588
- https://github.com/advisories/GHSA-hg6c-8mvr-jqc9
- https://osv.dev/vulnerability/MINI-3445-g9vq-rg27
- https://osv.dev/vulnerability/CVE-2026-42588
- https://lists.apache.org/thread/ns0zktfo16s9ql2mmtqtlb6p6xcs45xm
- http://www.openwall.com/lists/oss-security/2026/05/31/18
- https://github.com/strivepan/ActiveMQ-cve-2026-42588-scanner-gui