Apache ActiveMQ Improper Input Validation Vulnerability
Apache Software Foundation — Apache ActiveMQ Broker
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
8.8
97.2%
Vector breakdown
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- Apr 7, 2026
- Modified
- Aug 4, 2026
- Added to KEV
- Apr 16, 2026
- Federal patch due
- Apr 30, 2026
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Weakness classification
Affected packages
Proof-of-concept & exploitation references
8 foundWeaponization
Public repositories whose name or description references CVE-2026-34197, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
- Catherines77/ActiveMQ-EXPtools★ 83
Apache ActiveMQ漏洞综合利用工具(CVE-2015-5254，CVE-2016-3088，CVE-2022-41678，CVE-2023-46604，CVE-2024-32114，CVE-2026-34197，CVE-2026-40466， CVE-2026-42588)
updated Jul 25, 2026
- dinosn/apache-activemq-rce-research★ 9
Apache ActiveMQ Classic RCE research: CVE-2026-34197 / CVE-2026-42588 bypass chain + hardened-6.2.6 audit findings + Crowdfense comparison
updated Aug 26, 2026
- dinosn/CVE-2026-34197★ 8
CVE-2026-34197 activemq PoC
updated Jul 13, 2026
- DEVSECURITYSPRO/CVE-2026-34197★ 4
CVE-2026-34197 - Apache ActiveMQ RCE via Jolokia Endpoint PoC
updated May 6, 2026
- K3ysTr0K3R/CVE-2026-34197★ 3
CVE-2026-34197 - Apache ActiveMQ Jolokia Remote Code Execution (RCE)
updated Jul 26, 2026
- AtoposX-J/CVE-2026-34197-Apache-ActiveMQ-RCE★ 2
CVE-2026-34197
updated Jul 9, 2026
- KONDORDEVSECURITYCORP/CVE-2026-34197★ 2
CVE-2026-34197 — Apache ActiveMQ RCE via Jolokia API | PoC Exploit
updated Apr 27, 2026
- keraattin/CVE-2026-34197★ 2
CVE-2026-34197: Apache ActiveMQ Classic RCE via Jolokia API (CVSS 8.8). Python & Nmap NSE detection scripts. A 13-year-old vulnerability allows remote code execution through the addNetworkConnector MBean operation. Unauthenticated on versions 6.0.0 to 6.1.1. Fixed in 5.19.4 and 6.2.3.
updated Jul 28, 2026
References
How this class of flaw gets exploited
Frequently asked questions
What is CVE-2026-34197?
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
How severe is CVE-2026-34197?
CVE-2026-34197 has a CVSS base score of 8.8 out of 10 (CVSS 3.1).
Is CVE-2026-34197 actively exploited in the wild?
Yes. CVE-2026-34197 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Apr 16, 2026, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2026-34197?
97.2% - meaning FIRST.org's EPSS model estimates a 97.2% probability this vulnerability will be exploited in the wild within 30 days (100% percentile among all scored CVEs).
Is there exploit tooling available for CVE-2026-34197?
Yes - a public Nuclei template referencing CVE-2026-34197 exist in public repositories we checked. We also found 8 public GitHub repositories referencing this CVE.
What type of vulnerability is CVE-2026-34197?
CVE-2026-34197 is classified under CWE-20, CWE-78, CWE-94 (CWE-20 Improper Input Validation).
Cross-checked against
Impactr finds and proves whether CVE-2026-34197 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist