CVE-2026-34197
Improper Input Validation, Improper Control of Generation of Code ('Code Injection') vulnerability in Apache ActiveMQ Broker, Apache ActiveMQ…
Browse: All 2026 CVEs · All vendors
- CVSS score
- 8.8 High
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- CISA KEV
- Yes — actively exploited (added 2026-04-16, remediation due 2026-04-30)
- Weakness (CWE)
- CWE-20, CWE-94, CWE-78
- Published
- 2026-04-07
- Last modified
- 2026-08-04
- NVD status
- Analyzed
Description
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
Affected products
- apache activemq
- apache activemq broker
Affected ranges per NVD CPE data; confirm exact versions in the vendor advisory.
Required action (CISA)
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Federal remediation deadline: 2026-04-30.
How to prioritize this
This vulnerability is on the CISA KEV list, meaning it is being actively exploited — treat it as urgent regardless of the raw CVSS number. Use the live CVE lookup for the latest NVD data, and the CVSS 3.1 calculator to model your own environmental score.
References
- https://activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt
- http://www.openwall.com/lists/oss-security/2026/04/06/3
- https://access.redhat.com/security/cve/CVE-2026-34197
- https://bugzilla.redhat.com/show_bug.cgi?id=2455869
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34197.json
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-34197
FAQ
Is CVE-2026-34197 actively exploited?
Yes. CISA added CVE-2026-34197 to its Known Exploited Vulnerabilities (KEV) catalog on 2026-04-16, with a federal remediation deadline of 2026-04-30. A KEV listing means real-world exploitation is confirmed, so patching this should be prioritized above many higher-CVSS bugs that aren't being exploited.
What is the CVSS score of CVE-2026-34197?
CVE-2026-34197 has a CVSS base score of 8.8 (High). Its vector string is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Related vulnerabilities
- CVE-2023-46604 — Apache ActiveMQ
- CVE-2016-3088 — Apache ActiveMQ
- CVE-2026-34486 — Apache Tomcat
- CVE-2024-38475 — Apache HTTP Server
- CVE-2025-24813 — Apache Tomcat
- CVE-2024-45195 — Apache OFBiz
Data source: NVD & CISA KEV. Shown as-is; nothing added. Last generated from NVD data — re-check the live tool for updates.
weekly kev brief
Patch what's actually being exploited.
One email a week: the KEV additions that matter, prioritized — no noise.
Free. No spam. Unsubscribe anytime. Delivered by Beehiiv.