CVE-2026-34197

CRITICALPre-NVD 8.89.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-04-16), indicating real-world exploitation has been confirmed by US federal agencies. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa-adp, cisa_kev, epss
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 97%CVSS: 8.8Exploit: cisa kev · ssvc active · Metasploit · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
8.8
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
97%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

April 7, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-34197
generic

oss-security - CVE-2026-34197: Apache ActiveMQ Broker, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeans

http://www.openwall.com/lists/oss-security/2026/04/06/3
generic
https://activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt

Affected Packages

(5 across 4 ecosystems)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.apache.activemq:activemq-all6.0.0 ... 6.2.2 (14 versions)6.2.3—
org.apache.activemq:activemq-broker6.0.0 ... 6.2.2 (14 versions)6.2.3—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
activemq5.16.1-1 ... 5.17.6+dfsg-2 (8 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
activemq5.17.2+dfsg-2, 5.17.2+dfsg-2+deb12u1, 5.17.6+dfsg-1, 5.17.6+dfsg-2——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
activemq5.17.6+dfsg-2——

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 117 total refreshes for this CVE.

  1. 2026-08-31 14:19 UTCCISA KEV update
  2. 2026-08-30 19:46 UTCEG score recompute
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-29 00:33 UTCEG score recompute
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 17:22 UTCCISA KEV update
  7. 2026-08-26 17:41 UTCCISA KEV update
  8. 2026-08-24 18:52 UTCCISA KEV update
  9. 2026-08-24 16:50 UTCEG score recompute
  10. 2026-08-24 14:17 UTCEPSS rescore
  11. 2026-08-24 12:31 UTCEG score recompute
  12. 2026-08-21 16:49 UTCCISA KEV update
  13. 2026-08-20 17:06 UTCCISA KEV update
  14. 2026-08-19 17:33 UTCCISA KEV update
  15. 2026-08-18 16:58 UTCCISA KEV update
  16. 2026-08-17 13:56 UTCCISA KEV update
  17. 2026-08-16 18:52 UTCEG score recompute
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-11 19:32 UTCCISA KEV update
  20. 2026-08-11 13:45 UTCEG score recompute
  21. 2026-08-07 17:09 UTCCISA KEV update
  22. 2026-08-05 17:25 UTCCISA KEV update
  23. 2026-08-04 17:02 UTCCISA KEV update
  24. 2026-08-03 19:22 UTCCISA KEV update
  25. 2026-07-30 09:25 UTCEG score recompute
Show 75 more
  1. 2026-07-29 19:27 UTCCISA KEV update
  2. 2026-07-27 19:24 UTCCISA KEV update
  3. 2026-07-27 17:17 UTCCISA KEV update
  4. 2026-07-27 16:33 UTCEG score recompute
  5. 2026-07-27 14:13 UTCEPSS rescore
  6. 2026-07-26 18:58 UTCEG score recompute
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 14:39 UTCEG score recompute
  10. 2026-07-26 01:38 UTCEG score recompute
  11. 2026-07-24 14:17 UTCEPSS rescore
  12. 2026-07-24 14:17 UTCEPSS rescore
  13. 2026-07-23 03:09 UTCEG score recompute
  14. 2026-07-22 19:40 UTCCISA KEV update
  15. 2026-07-21 14:37 UTCCISA KEV update
  16. 2026-07-20 20:49 UTCEG score recompute
  17. 2026-07-20 17:08 UTCEPSS rescore
  18. 2026-07-17 10:48 UTCEG score recompute
  19. 2026-07-16 17:04 UTCCISA KEV update
  20. 2026-07-15 16:49 UTCCISA KEV update
  21. 2026-07-15 15:04 UTCCISA KEV update
  22. 2026-07-14 18:05 UTCCISA KEV update
  23. 2026-07-13 17:07 UTCCISA KEV update
  24. 2026-07-10 17:52 UTCCISA KEV update
  25. 2026-07-08 15:15 UTCEPSS rescore
  26. 2026-07-07 19:01 UTCCISA KEV update
  27. 2026-07-07 17:16 UTCCISA KEV update
  28. 2026-07-01 19:16 UTCCISA KEV update
  29. 2026-07-01 15:06 UTCEPSS rescore
  30. 2026-06-30 23:22 UTCEPSS rescore
  31. 2026-06-29 19:12 UTCCISA KEV update
  32. 2026-06-25 19:15 UTCCISA KEV update
  33. 2026-06-23 21:33 UTCEPSS rescore
  34. 2026-06-23 21:33 UTCEPSS rescore
  35. 2026-06-23 17:44 UTCCISA KEV update
  36. 2026-06-21 14:56 UTCEPSS rescore
  37. 2026-06-21 14:56 UTCEPSS rescore
  38. 2026-06-18 16:13 UTCCISA KEV update
  39. 2026-06-17 17:53 UTCEPSS rescore
  40. 2026-06-16 19:33 UTCCISA KEV update
  41. 2026-06-15 19:33 UTCCISA KEV update
  42. 2026-06-15 17:49 UTCEPSS rescore
  43. 2026-06-14 23:18 UTCEPSS rescore
  44. 2026-06-12 23:12 UTCEPSS rescore
  45. 2026-06-12 23:12 UTCEPSS rescore
  46. 2026-06-12 17:35 UTCCISA KEV update
  47. 2026-06-11 19:10 UTCCISA KEV update
  48. 2026-06-11 14:00 UTCEPSS rescore
  49. 2026-06-10 22:18 UTCEPSS rescore
  50. 2026-06-10 13:22 UTCEPSS rescore
  51. 2026-06-09 18:42 UTCCISA KEV update
  52. 2026-06-09 17:12 UTCCISA KEV update
  53. 2026-06-08 19:16 UTCCISA KEV update
  54. 2026-06-08 17:26 UTCCISA KEV update
  55. 2026-06-08 14:17 UTCEPSS rescore
  56. 2026-06-08 14:17 UTCEPSS rescore
  57. 2026-06-07 15:25 UTCEPSS rescore
  58. 2026-06-07 15:25 UTCEPSS rescore
  59. 2026-06-07 15:25 UTCEPSS rescore
  60. 2026-06-05 22:47 UTCEPSS rescore
  61. 2026-06-05 22:47 UTCEPSS rescore
  62. 2026-06-05 22:43 UTCCISA KEV update
  63. 2026-06-04 13:12 UTCEPSS rescore
  64. 2026-06-04 13:12 UTCEPSS rescore
  65. 2026-06-03 19:09 UTCCISA KEV update
  66. 2026-06-02 20:13 UTCEPSS rescore
  67. 2026-06-02 18:32 UTCCISA KEV update
  68. 2026-06-01 20:42 UTCCISA KEV update
  69. 2026-06-01 13:52 UTCEPSS rescore
  70. 2026-06-01 13:52 UTCEPSS rescore
  71. 2026-06-01 13:51 UTCEPSS rescore
  72. 2026-05-31 22:30 UTCEPSS rescore
  73. 2026-05-31 22:30 UTCEPSS rescore
  74. 2026-05-31 00:16 UTCEPSS rescore
  75. 2026-05-31 00:16 UTCEPSS rescore

Publicly available exploits

(10 references)

Working exploit code is in the public domain (1 Metasploit module) (8 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCK3ysTr0K3R/CVE-2026-34197
    First seen Jul 16, 2026

    CVE-2026-34197 - Apache ActiveMQ Jolokia Remote Code Execution (RCE)

    Open source ↗
  • GitHub PoCdinosn/apache-activemq-rce-research
    First seen Jul 4, 2026

    Apache ActiveMQ Classic RCE research: CVE-2026-34197 / CVE-2026-42588 bypass chain + hardened-6.2.6 audit findings + Crowdfense comparison

    Open source ↗
  • Metasploitexploit/multi/http/apache_activemq_jolokia_rce✓ verified
    First seen Apr 29, 2026

    Apache ActiveMQ RCE via Jolokia addNetworkConnector

    Open source ↗
  • GitHub PoCCatherines77/ActiveMQ-EXPtools
    First seen Apr 20, 2026

    Apache ActiveMQ漏洞综合利用工具(CVE-2015-5254，CVE-2016-3088，CVE-2022-41678，CVE-2023-46604，CVE-2024-32114，CVE-2026-34197，CVE-2026-40466)

    Open source ↗
  • GitHub PoCkeraattin/CVE-2026-34197
    First seen Apr 14, 2026

    CVE-2026-34197: Apache ActiveMQ Classic RCE via Jolokia API (CVSS 8.8). Python & Nmap NSE detection scripts. A 13-year-old vulnerability allows remote code execution through the addNetworkConnector MBean operation. Unauthenticated on versions 6.0.0 to 6.1.1. Fixed in 5.19.4 and 6.2.3.

    Open source ↗
  • GitHub PoCAtoposX-J/CVE-2026-34197-Apache-ActiveMQ-RCE
    First seen Apr 9, 2026

    CVE-2026-34197

    Open source ↗
  • GitHub PoCKONDORDEVSECURITYCORP/CVE-2026-34197
    First seen Apr 9, 2026

    CVE-2026-34197 — Apache ActiveMQ RCE via Jolokia API | PoC Exploit

    Open source ↗
  • GitHub PoCdinosn/CVE-2026-34197
    First seen Apr 8, 2026

    CVE-2026-34197 activemq PoC

    Open source ↗
  • GitHub PoCDEVSECURITYSPRO/CVE-2026-34197
    First seen Apr 8, 2026

    CVE-2026-34197 - Apache ActiveMQ RCE via Jolokia Endpoint PoC

    Open source ↗
  • Nucleihttp/cves/2026/CVE-2026-34197.yaml
    First seen Jan 1, 2026

    Apache ActiveMQ - Remote Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2026-34197?
CVE-2026-34197 is a critical vulnerability published on April 7, 2026. 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…
When was CVE-2026-34197 disclosed?
CVE-2026-34197 was first published in the National Vulnerability Database on April 7, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34197 actively exploited?
Yes. CISA added CVE-2026-34197 to the Known Exploited Vulnerabilities catalog on April 16, 2026, affecting Apache ActiveMQ. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2026-34197?
CVE-2026-34197 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2026-34197?
CVE-2026-34197 affects Apache ActiveMQ. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2026-34197?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34197, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-34197

Explore →

Is Your Infrastructure Affected by CVE-2026-34197?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs