CVE-2026-34197: Apache ActiveMQ Jolokia MBean code injection (authenticated RCE)
Exploited in the wild High 8.8 EPSS 98.3% Apache ActiveMQ
ActiveMQ Classic exposes the Jolokia JMX-HTTP bridge at /api/jolokia/ on the web console, and its default policy allows exec operations such as BrokerService.addNetworkConnector; an authenticated attacker can pass a crafted discovery URI that loads a remote Spring XML context and runs code in the broker's JVM. Fixed in 5.19.4 and 6.2.3 (7 April 2026); CISA added it to KEV on 16 April 2026.
- CVE-2026-34197CVE identifier
- 8.8CVSS 3.1 base score (high)
- 2026-04-16added to CISA's exploited list (US federal deadline 2026-04-30)
- 98.3%EPSS: chance of exploitation in the next 30 days (higher than 100% of CVEs)
- 2026-04-07published
What do these terms mean? CVE · CVSS score · exploited (KEV) · EPSS · backported fix · all terms
What to do now
- Check whether you run Apache ActiveMQ and which version (commands below).
- Install the fixed version for your system: see “Patch it” below.
- Restart the ActiveMQ broker.
- If you cannot patch today, apply the temporary mitigation below and patch as soon as possible.
- Because this flaw is being exploited, also check the server for signs of compromise.
Affected and fixed versions
Affected:
- Apache ActiveMQ before 5.19.4
- Apache ActiveMQ 6.0.0 before 6.2.3
Fixed in:
- Apache ActiveMQ 5.19.4
- Apache ActiveMQ 6.2.3
Am I affected?
ls $ACTIVEMQ_HOME/lib | grep activemq-broker
dpkg -l activemq | grep ^ii # Debian/Ubuntu package (no fix yet)
Patch it
Use the commands for your system. Distribution packages often keep an older version number with the fix backported, so compare with the fixed package versions in the table below, not only with the upstream version.
Debian
sudo apt update
sudo apt install --only-upgrade activemqUbuntu
sudo apt update
sudo apt install --only-upgrade activemqRHEL, AlmaLinux, Rocky, Oracle
not packaged: upstream tarballFedora
not packagedSUSE / openSUSE
not packagedAmazon Linux
not packaged: Amazon MQ is managedArch Linux
not in official reposAlpine
not packagedFreeBSD
pkg update && pkg upgrade activemqDocker images
# switch to an image built on ActiveMQ 5.19.4+ or 6.2.3+, then recreate the containerBuilt from source
# install Apache ActiveMQ 5.19.4+ or 6.2.3+ from https://activemq.apache.org/ and restart the brokerGeneral update steps for every system are on the Linux and Unix & BSD pages; after updating, see which services to restart.
Fix status in Linux distributions
| Release | Package | Status | Fixed version / advisory |
|---|---|---|---|
| Debian 12 | activemq | not fixed yet | |
| Debian 13 | activemq | not fixed yet | |
From the Debian security tracker, Ubuntu CVE tracker and Red Hat Security Data API, refreshed every few hours.
If you cannot patch yet
- Debian lists its bookworm and trixie activemq packages as vulnerable and Ubuntu has not yet triaged its packages, so use the upstream release.
- The flaw is reached through the web console's Jolokia endpoint (/api/jolokia/); keep the web console off untrusted networks.
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.
https://activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt ; https://nvd.nist.gov/vuln/detail/CVE-2026-34197
Sources
- CVE record CVE-2026-34197
- NVD CVE-2026-34197
- CISA KEV entry CVE-2026-34197
- Debian security tracker CVE-2026-34197
- Ubuntu CVE page CVE-2026-34197
- Red Hat CVE page CVE-2026-34197
- Apache ActiveMQ announcement CVE-2026-34197
- CISA Known Exploited Vulnerabilities catalog
Page generated automatically from official sources on 2026-11-03 18:05 UTC and reviewed by an editor. Always confirm with your vendor's advisory.