Authenticated Apache ActiveMQ Broker and Apache ActiveMQ users could perform RCE via Jolokia MBeans
CVE-2026-34197GHSA-rxpj-7qvf-xv32
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.apache.activemq:activemq-broker 6.2.3, 5.19.5; org.apache.activemq:activemq-all 6.2.3, 5.19.5), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.apache.activemq:activemq-broker
- Affected
- < 5.19.5>= 6.0.0, < 6.2.3
- Fixed in
- 5.19.5, 6.2.3
Maven org.apache.activemq:activemq-all
- Affected
- < 5.19.5>= 6.0.0, < 6.2.3
- Fixed in
- 5.19.5, 6.2.3
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-rxpj-7qvf-xv32 lists affected ranges: Maven org.apache.activemq:activemq-broker >=0 =6.0.0 =0 =6.0.0 <6.2.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- CISA Known Exploited Vulnerabilities Catalog
CISA added CVE-2026-34197 to the Known Exploited Vulnerabilities catalog on 2026-04-16.
VerifiedObserved Listed in the CISA KEV JSON feed (dateAdded 2026-04-16).
Severity and exploitation
- Exploitation
- Confirmed: listed in the CISA Known Exploited Vulnerabilities catalog.
- CVSS
- 8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2026-34197: 98.26% estimated exploitation activity in the next 30 days; percentile 99.92 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-rxpj-7qvf-xv32
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-34197 Advisory: Authenticated Apache ActiveMQ Broker and Apache ActiveMQ users could perform RCE via Jolokia MBeans IDs: CVE-2026-34197, GHSA-rxpj-7qvf-xv32 Record: https://patchnext.com/advisories/cve-2026-34197 (revision 1, source checked 26 Oct 2026, 16:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.8) Exploitation: confirmed: listed in the CISA Known Exploited Vulnerabilities catalog. Vendor response: Vendor fix available; fixed versions by package: org.apache.activemq:activemq-broker 6.2.3, 5.19.5; org.apache.activemq:activemq-all 6.2.3, 5.19.5. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.apache.activemq:activemq-broker: affected < 5.19.5; >= 6.0.0, < 6.2.3; fixed in 5.19.5, 6.2.3 - Maven org.apache.activemq:activemq-all: affected < 5.19.5; >= 6.0.0, < 6.2.3; fixed in 5.19.5, 6.2.3 ## Suggested inspection (read-only) - Maven org.apache.activemq:activemq-broker: check the installed version with your package manager. - Maven org.apache.activemq:activemq-all: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.apache.activemq:activemq-broker, org.apache.activemq:activemq-all. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-rxpj-7qvf-xv32 (GitHub-reviewed advisory GHSA-rxpj-7qvf-xv32 lists affected ranges: Maven org.apache.activemq:activemq-broker >=0 =6.0.0 =0 =6.0.0 <6.2.3) - Verified: https://www.cisa.gov/known-exploited-vulnerabilities-catalog (CISA added CVE-2026-34197 to the Known Exploited Vulnerabilities catalog on 2026-04-16.) Commands are suggestions: review each one before running it.
Loading voting…