CVE-2026-34197

HIGHPre-NVD 8.89.0
EchelonGraph scoreMEDIUM 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
Exploited in the wild
8.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 97%CVSS: 8.8Exploit: NoneExposed: 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(medium)
EPSS
99.9%
KEV
⚠ Exploited

Published

April 7, 2026

Last Modified

July 15, 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

Affected Packages

(2 across 1 ecosystem)
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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 44× in last 7d / 187× 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 334 total refreshes for this CVE.

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

Publicly available exploits

(4 references)

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

  • 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 ↗
  • Nucleihttp/cves/2026/CVE-2026-34197.yaml
    First seen Jan 1, 2026

    Apache ActiveMQ - Remote Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2026-34197?
CVE-2026-34197 is a high 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 July 15, 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.