Skip to content
Fencer Vulns
high 8.1

CVE-2026-42588 json

Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Remote Code Execution via Jolokia addNetworkConnector

published 2026-06-01 5 mo ago modified 2026-09-10 1 mo ago also BIT-activemq-2026-42588 , EUVD-2026-33577 , GHSA-hg6c-8mvr-jqc9

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.apache.activemq:activemq-broker 5.19.7, 6.2.6
  • maven org.apache.activemq:activemq-all 5.19.7, 6.2.6
  • maven org.apache.activemq:apache-activemq 5.19.7, 6.2.6
  • bitnami activemq 5.19.7, 6.2.6
  • Apache Software Foundation Apache ActiveMQ Broker 5.19.7, 6.2.6
  • Apache Software Foundation Apache ActiveMQ All 5.19.7, 6.2.6
  • Apache Software Foundation Apache ActiveMQ 5.19.7, 6.2.6

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-42588 updated cvss 8.1

org.apache.activemq/activemq-broker: org.apache.activemq/activemq-all: org.apache.activemq/apache-activemq: Apache ActiveMQ: Arbitrary code execution via improper input validation in Jolokia JMX-HTTP

  • Red Hat Fuse 7 activemq-all, activemq-broker
    affected: workaround, no fix planned “Will not fix”
  • Red Hat AMQ Broker 7.13.6
    fixed: vendor fix RHSA-2026:66545
  • Red Hat AMQ Broker 7.14.1
    fixed: vendor fix RHSA-2026:66488
  • Red Hat Data Grid 8 activemq-broker Red Hat JBoss Enterprise Application Platform Expansion Pack activemq-broker
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
5 mo ago

Exploit prediction

0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
OSV 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.activemq:activemq-broker
<5.19.7
>=6.0.0, <6.2.6
5.19.7
6.2.6
maven org.apache.activemq:activemq-all
<5.19.7
>=6.0.0, <6.2.6
5.19.7
6.2.6
maven org.apache.activemq:apache-activemq
<5.19.7
>=6.0.0, <6.2.6
5.19.7
6.2.6
bitnami activemq
<5.19.7
>=6.0.0, <6.2.6
5.19.7
6.2.6

Affected products

  • Apache Software Foundation Apache ActiveMQ Broker
  • Apache Software Foundation Apache ActiveMQ All
  • Apache Software Foundation Apache ActiveMQ

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.