CVE-2026-34197: Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeans
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
Security readout for executives and security teams
Plain-English summary
CVE-2026-34197 lets a logged-in attacker turn Apache ActiveMQ Classic’s web management interface into code execution on the broker server. Because CISA lists it in KEV, organizations should treat affected internet-reachable or broadly accessible brokers as urgent.
Executive priority
Treat this as a near-term remediation priority. It combines authenticated remote code execution, low attack complexity, full system impact, and CISA KEV evidence of exploitation.
Technical view
ActiveMQ Classic exposes Jolokia at /api/jolokia/. The default policy permits exec operations on ActiveMQ MBeans. An authenticated attacker can abuse connector MBean operations with crafted input that causes Spring ResourceXmlApplicationContext bean instantiation before validation, resulting in JVM-level remote code execution.
Likely exposure
Exposure is most likely where Apache ActiveMQ Classic web console or Jolokia access is enabled and reachable by non-administrative or compromised authenticated users. Affected versions are before 5.19.4 and 6.0.0 through before 6.2.3.
Exploitation context
The source bundle states CISA KEV status, so active exploitation is supported. The vulnerability requires network access, low privileges, and no user interaction, with high confidentiality, integrity, and availability impact.
Researcher notes
Evidence supports the Jolokia-to-MBean execution path and affected version ranges. The bundle does not provide safe detection signatures, exploit prevalence, or product-specific downstream vendor status beyond listed references.
Mitigation direction
Upgrade Apache ActiveMQ Classic to 5.19.4 or 6.2.3.
Prioritize brokers with reachable web console or Jolokia endpoints.
Limit ActiveMQ administrative access to trusted management networks and accounts.
Review Apache guidance before relying on compensating controls.
Monitor vendor and CISA updates for revised remediation guidance.
Validation and detection
Inventory ActiveMQ Broker, ActiveMQ All, and Apache ActiveMQ package versions.
Confirm all affected deployments run 5.19.4, 6.2.3, or later.
Check whether /api/jolokia/ is enabled and reachable.
Review authentication logs for unexpected web console or Jolokia access.
Review broker logs for unusual connector or network-connector changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
ADP timelineredhat-SADP
Made public.
Apr 7, 2026, 07:50 UTC (UTC+00:00)
CVE publishedCVE Program
The CVE record was published.
Apr 7, 2026, 07:50 UTC (UTC+00:00)
ADP timelineredhat-SADP
Reported to Red Hat.
Apr 7, 2026, 09:01 UTC (UTC+00:00)
Added to KEVCISA-ADP
CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.
Apr 16, 2026, 00:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Jul 15, 2026, 01:04 UTC (UTC+00:00)
ADP provider summaries
CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvcother:kev
redhat-SADPorg.apache.activemq/activemq-broker: org.apache.activemq/activemq-all: Apache ActiveMQ: RCE via crafted discovery URI in Jolokia JMX-HTTP bridge