Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Evidence dossier
CVE-2026-34197
Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeans
gen-56ccdaf9Normalized restatement
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, 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) and BrokerService.addConnector(String). An authenticated attacker can invoke these operations with a crafted discovery URI that triggers the VM transport's brokerConfig parameter to load a remote 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.4, from 6.0.0 before 6.2.3; Apache ActiveMQ All: before 5.19.4, from 6.0.0 before 6.2.3; Apache ActiveMQ: before 5.19.4, from 6.0.0 before 6.2.3. Users are recommended to upgrade to version 5.19.4 or 6.2.3, which fixes the issue
- State
- PUBLISHED
- Published
- Apr 7, 2026
- Updated
- Jul 15, 2026
- Evidence coverage
- 85%
2026-07-18 · v2026.06.15 · percentile 99.9%
Distinct CVSS assessments remain side by side; none are averaged.
Source comparison
Who said what
Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeans
org.apache.activemq/activemq-broker: org.apache.activemq/activemq-all: Apache ActiveMQ: RCE via crafted discovery URI in Jolokia JMX-HTTP bridge
Apache ActiveMQ Improper Input Validation Vulnerability
Probability 0.966660000000; percentile 0.998770000000
Applicability
Cited product scope
[{"status": "affected", "version": "0", "lessThan": "5.19.4", "versionType": "semver"}, {"status": "affected", "version": "6.0.0", "lessThan": "6.2.3", "versionType": "semver"}]unknown[{"status": "affected", "version": "0", "lessThan": "5.19.4", "versionType": "semver"}, {"status": "affected", "version": "6.0.0", "lessThan": "6.2.3", "versionType": "semver"}]unknown[{"status": "affected", "version": "0", "lessThan": "5.19.4", "versionType": "semver"}, {"status": "affected", "version": "6.0.0", "lessThan": "6.2.3", "versionType": "semver"}]unknown[]unknown[]unknown[]unknown[]unknown[]unknown[]unknown[]unknown[]unknown[]unknowncpe:2.3:a:apache:activemq:*:*:*:*:*:*:*:*; end excluding 5.19.4supportedcpe:2.3:a:apache:activemq:*:*:*:*:*:*:*:*; start including 6.0.0; end excluding 6.2.3supportedcpe:2.3:a:apache:activemq_broker:*:*:*:*:*:*:*:*; end excluding 5.19.4supportedcpe:2.3:a:apache:activemq_broker:*:*:*:*:*:*:*:*; start including 6.0.0; end excluding 6.2.3supportedAssessments
CVSS by origin
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLimitations and unknowns
- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.