What is CVE-2026-34197?
Critical remote code execution vulnerability in Apache ActiveMQ Classic residing in the interaction between the Jolokia JMX-HTTP bridge, the broker's network connector management API, and Spring Framework's XML application context loading mechanism. The Jolokia REST API at /api/jolokia/ permits exec operations on all ActiveMQ MBeans due to an overly permissive allowlist introduced after the CVE-2022-41678 fix. An attacker invokes BrokerService.addNetworkConnector() with a crafted VM transport URI containing a brokerConfig=xbean:http:// parameter pointing to a malicious Spring XML file. Spring's ResourceXmlApplicationContext fetches the remote XML and instantiates singleton beans — including MethodInvokingFactoryBean calling Runtime.exec() — before the BrokerService validates the configuration, yielding reliable arbitrary OS command execution. Exploitation requires Jolokia authentication (default admin:admin widely deployed), but on ActiveMQ 6.0.0-6.1.1 the vulnerability is effectively unauthenticated due to CVE-2024-32114 exposing the Jolokia API without access control. The flaw existed undetected for approximately 13 years.
The record classifies CVE-2026-34197 under weakness classes CWE-20, CWE-94. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity, availability. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 187 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 8.8 — HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS (FIRST)
- 84.1% probability of exploitation in the next 30 days, higher than 99.3% of all scored CVEs
- CISA KEV
- Listed since 2026-04-16, federal remediation deadline 2026-04-30
- Threadlinqs priority
- 9/10 — CISA KEV-listed, which Threadlinqs floors at 9
- Published
- 2026-04-01, last modified 2026-04-08
Is CVE-2026-34197 being exploited?
CISA added CVE-2026-34197 to the Known Exploited Vulnerabilities catalog on 2026-04-16, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-04-30 under BOD 22-01. It currently carries a trending score of 40 in the Threadlinqs vulnerability feed.
Affected products and versions
- Apache: ActiveMQ Classic
How to fix CVE-2026-34197
The record marks a vendor fix as available for CVE-2026-34197. Vendor advisory: https://activemq.apache.org/security-advisories. Because CVE-2026-34197 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-04-30. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.
Threat activity tracking CVE-2026-34197
2 tracked threats in the Threadlinqs corpus reference CVE-2026-34197, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Seeded from threat-derived and not yet processed by the Threadlinqs enrichment pipeline, so blank CVSS, EPSS or KEV fields above mean NOT MEASURED rather than measured-absent.