Detect Apache ActiveMQ Improper Input Validation (CVE-2026-34197) in Google Chronicle
Detects exploitation of CVE-2026-34197, an improper input validation vulnerability (CWE-20/CWE-94) in Apache ActiveMQ that has been added to the CISA Known Exploited Vulnerabilities catalog. Successful exploitation may allow remote attackers to execute arbitrary code or inject malicious content via crafted messages or broker connections. ActiveMQ's OpenWire protocol and web console are common attack surfaces for this class of vulnerability.
MITRE ATT&CK
- Tactic
- Initial Access Execution Persistence
YARA-L Detection Query
rule cve_2026_34197_activemq_exploitation {
meta:
author = "df00tech Detection Engineering"
description = "Detects CVE-2026-34197 Apache ActiveMQ improper input validation exploitation"
severity = "CRITICAL"
priority = "HIGH"
reference = "https://activemq.apache.org/security-advisories.data/CVE-2026-34197-announcement.txt"
tags = "cve-2026-34197, activemq, cwe-20, cwe-94, kev"
events:
(
// Network event to ActiveMQ ports
$net.metadata.event_type = "NETWORK_CONNECTION"
$net.target.port in (61616, 61617, 8161, 8162, 5672, 1883, 61613)
$net.principal.ip != "127.0.0.1"
(
$net.network.http.request_url = /ClassPathXmlApplicationContext/ nocase or
$net.network.http.request_url = /\.\.\/\.\.\// nocase or
$net.metadata.description = /classInfo|ExceptionResponse/ nocase
)
)
or
(
// Process launched as child of ActiveMQ/Java with suspicious commands
$proc.metadata.event_type = "PROCESS_LAUNCH"
$proc.principal.process.file.full_path = /activemq|java/ nocase
$proc.target.process.file.full_path = /cmd\.exe|powershell|bash|sh|wget|curl|ncat|python/ nocase
)
condition:
$net or $proc
}Chronicle YARA-L 2.0 rule detecting CVE-2026-34197 Apache ActiveMQ exploitation via network connections containing known malicious payload patterns or anomalous child process spawning from ActiveMQ/Java parent processes.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate Spring Framework message-driven beans that reference ClassPathXmlApplicationContext in payload content
- Authorized penetration tests or red team operations against ActiveMQ deployments
- Java process management tools that spawn shell interpreters for lifecycle management
Other platforms for CVE-2026-34197
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1ActiveMQ OpenWire Port Probe with Malicious Payload Pattern
Expected signal: Network connection event to port 61616 from non-standard source; payload content containing 'ClassPathXmlApplicationContext' visible in network capture or IDS alerts
- Test 2Simulated Post-Exploitation Shell Spawn from Java Process
Expected signal: Sysmon Event ID 1 or Linux audit execve showing bash/sh spawned with parent process containing 'java' in the image path; process command line containing 'id', 'hostname', or 'whoami'
- Test 3ActiveMQ Web Console Access with Path Traversal Attempt
Expected signal: HTTP access log entries on port 8161 containing '../' path sequences and 'ClassPathXmlApplicationContext' in request body or destination parameter; network connection events to port 8161 from unexpected source
Unlock Pro Content
Get the full detection package for CVE-2026-34197 including response playbook, investigation guide, and atomic red team tests.