What is CVE-2026-34197?

CVE-2026-34197 is Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeans. The supplied enrichment data classifies it as Remote Code Exec mapped to CWE-20 Improper Input Validation; CWE-94 Code Injection; CWE-78 OS Command Injection.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

40 public PoC repositories reported; 3 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS, EDR process telemetry, host service logs where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-34197 using CVSS 8.8, EPSS 97%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighRemote Code Execpublic exploit

CVE-2026-34197

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

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-34197 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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

Published Apr 7, 2026Updated Jul 15, 2026Sources: NVD, Apache Software Foundation (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Apr 16, 2026

EPSS

97%

ahead of 99.9% of scored CVEs

Affects

Apache

10 products listed

CVSS base

8.8

high

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade org.apache.activemq:activemq-broker to 5.19.5 or later (maven advisory GHSA-rxpj-7qvf-xv32).

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.

Federal deadline Apr 30, 2026 — passed 115 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Apache	Apache ActiveMQ Broker	0 to < 5.19.4	Vulnerable
Apache	Apache ActiveMQ Broker	6.0.0 to < 6.2.3	Vulnerable
Apache	Apache ActiveMQ All	0 to < 5.19.4	Vulnerable
Apache	Apache ActiveMQ All	6.0.0 to < 6.2.3	Vulnerable
Apache	Apache ActiveMQ	0 to < 5.19.4	Vulnerable
Apache	Apache ActiveMQ	6.0.0 to < 6.2.3	Vulnerable
maven	org.apache.activemq:activemq-broker	< 5.19.5	Vulnerable
maven	org.apache.activemq:activemq-broker	>= 6.0.0, < 6.2.3	Vulnerable
maven	org.apache.activemq:activemq-all	< 5.19.5	Vulnerable
maven	org.apache.activemq:activemq-all	>= 6.0.0, < 6.2.3	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
8.8	CVSS 3.1	high	2.8	5.9	CNA, GHSA

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

Weakness & attack patterns

CWE-20Improper Input Validation
CWE-94Code Injection
CWE-78OS Command Injection

Inferred from the weakness class — not observed against this CVE.

CAPEC-242 · Code InjectionCAPEC-35 · Leverage Executable Code in Non-Executable Files

T1562.003Impair Defenses: Impair Command History Logging
T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Apr 16, 2026

Federal deadline

Apr 30, 2026

passed 115 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

3 of the 5 sampled are weaponized

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /api/jolokia/.
Prioritize edge telemetry for network-reachable Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ, org.apache.activemq:activemq-broker, org.apache.activemq:activemq-all.
Monitor for scanner or exploit-pattern traffic after 40 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 8.8 (AV:N)
Jul 15, 2026 · NVD
Added to CISA KEV catalog
Apr 16, 2026 · CISA
Initial · CVE published
Apr 7, 2026 · NVD
Added · GHSA-rxpj-7qvf-xv32 published (high)
Apr 7, 2026 · GitHub Security Advisory

References

8 on the record

activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt
Vendor Advisory
www.openwall.com/lists/oss-security/2026/04/06/3
Mailing List, Third Party Advisory
access.redhat.com/security/cve/CVE-2026-34197
Third Party Advisory
bugzilla.redhat.com/show_bug.cgi?id=2455869
Third Party Advisory
security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-34197.json
Third Party Advisory
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-34197
US Government Resource
nvd.nist.gov/vuln/detail/CVE-2026-34197
NVD, Vendor Advisory
github.com/advisories/GHSA-rxpj-7qvf-xv32
Exploit, Third Party Advisory

Elsewhere on this site

Apacheevery CVE for this vendor
mavenevery CVE for this vendor
April 2026what else CISA listed
Remote Code Execsame class
CWE-20other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-34197 is Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ: Authenticated users could perform RCE via Jolokia MBeans, a high vulnerability affecting Apache ActiveMQ Broker, Apache ActiveMQ All, Apache ActiveMQ, org.apache.activemq:activemq-broker, org.apache.activemq:activemq-all from Apache Software Foundation, maven. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 40 public PoC repositories reported; 3 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 8.8 describes technical severity, while EPSS 97% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.