CVE Tools

CVE-2026-34197

Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeans

Exploited in the wild. In CISA KEV since 2026‑04‑16. Fixed versions are out.

Published Updated Sources: CVE.org, NVD, BDU, CSAF

What to do

Find your product and version, then upgrade to the build on the right.

  • Apache Software Foundation Apache ActiveMQ BrokerAffected: < 5.19.4Upgrade to: 5.19.4Affected: ≥ 6.0.0, < 6.2.3Upgrade to: 6.2.3Stated by: CVE record
  • Apache Software Foundation Apache ActiveMQ AllAffected: < 5.19.4Upgrade to: 5.19.4Affected: ≥ 6.0.0, < 6.2.3Upgrade to: 6.2.3Stated by: CVE record
  • Apache Software Foundation Apache ActiveMQAffected: < 5.19.4Upgrade to: 5.19.4Affected: ≥ 6.0.0, < 6.2.3Upgrade to: 6.2.3Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Coverage timeline

0 publishers
  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened. 5 further articles named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

Hitachi Energy is aware of RCE (Remote Code Execution) vulnerability in Apache ActiveMQ component of SOI product versions listed in this document. These vulnerabilities can be exploited to carry out various attacks affecting confidentiality, integrity, and availability of the product. Please refer to the Recommended Immediate Actions for information about the mitigation/remediation.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS97th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2026-04-16.

US federal agencies must remediate by 2026-04-30.

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

15% chance of exploitation activity in the next 30 days, which ranks it in the 97th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

21 events over 176 days, from the signal feeds we watch.

  1. EPSS band changecritical → moderate
  2. EPSS band changecritical → moderateepss band change
  3. Patch availablerecord updated
  4. Patch availablerecord updated
  5. Patch availablerecord updated
  6. EPSS band changehigh → critical

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 8.8 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apache ActiveMQ Broker, not every advisory. This one: actively exploited.