CVE-2026-34197
Exploitation confirmed. First attested on 2026-04-16 by CISA-ADP, CISA KEV, GCVE · kevintel, GCVE · shadowserver.
- Published2026-04-07
- Fixed in6.2.3 · 5.19.4
- WeaknessCWE-20 · CWE-78 · CWE-94
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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
Timeline
dates in UTC- 2026-04-0709:16CVE publishedNVD
- 2026-04-16Listed as exploited by GCVEGCVE
- 2026-04-16Exploitation first reportedCISA KEV
- 2026-04-16Added to the CISA KEV catalogCISA KEV
- 2026-04-1703:55SSVC exploitation set to activeCISA-ADP
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-34197?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-34197?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.x | ≥ 6.0.0, < 6.2.3 | 6.2.3 | NVD |
| 5.19 | < 5.19.4 | 5.19.4 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.x | ≥ 6.0.0, < 6.2.3 | 6.2.3 | NVD |
| 5.19 | < 5.19.4 | 5.19.4 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Hitachi Energy SOI
SOI Version 2.0.0 to 2.2.0
Fix
- Update Apache activemq to 6.2.3 · 5.19.4
- CISA’s 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.due 2026-04-30
- Vendor fix CISA ICSA-26-279-04 · 1 productApply the patch SOI EP2, which upgrades the ActiveMQ version (JMS message broker) for the SOI Core to version 5.19.5. EP2 is a cumulative patch that covers previous EP1 patch. EP2 also upgrades the SOI management scripts to the latest version and installs an upgraded OpenJDK version 11 to run Acti…
- Mitigation from the vendor CISA ICSA-26-279-04 · 1 productFollow General Mitigation Factors/Workarounds and refer to the product deployment guidelines for securing the product environment.
Advisories and patches
- activemq.apache.orgVendor Advisory
Detection
read 2026-10-23 19:25 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 15 repositories, unverified0xBlackash/CVE-2026-34197dinosn/CVE-2026-34197DEVSECURITYSPRO/CVE-2026-34197AtoposX-J/CVE-2026-34197-Apache-ActiveMQ-RCEKONDORDEVSECURITYCORP/CVE-2026-34197 PoC-in-GitHub
CISA Known Exploited Vulnerability
- Date Added
- 2026-04-16
- Patch Due Date
- 2026-04-30
- Ransomware Use
- Unknown
- 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.
Sources
- NVDCVE recordread 2026-10-23
- CISA KEVKEV entry2026-04-16
- GCVEexploitation2026-04-16
- CISA-ADPSSVC decisionactive2026-04-17
- OpenCVESSVC decisionactive—
- CISA-ADPCVSS 3.18.82026-04-07
- CNACVSS 3.18.8read 2026-10-23
- CNAweakness (CWE)CWE-20, CWE-78, CWE-94read 2026-10-23
- FIRST EPSSEPSS score15.5 %read 2026-10-23
- PoC-in-GitHubproof of concept15read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2026-04-07
- Last Modified
- 2026-08-04
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2026-34197?
Is CVE-2026-34197 actively exploited?
What is the CVSS score for CVE-2026-34197?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.