Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-34486.

Unlock with Pro - from £29/user/mo
CVE-2026-34486 Google Chronicle · YARA-L

Detect Apache Tomcat Missing Encryption of Sensitive Data (CVE-2026-34486) in Google Chronicle

Detects potential exploitation or exposure conditions related to CVE-2026-34486, an Apache Tomcat vulnerability (CWE-311: Missing Encryption of Sensitive Data) allowing sensitive data such as credentials, session identifiers, or configuration secrets to be transmitted or stored without adequate encryption. Actively exploited and listed in CISA KEV; associated with CISA BOD 26-04 prioritized remediation guidance. Detection focuses on plaintext transmission of Tomcat-managed credentials/session tokens over unencrypted channels, anomalous access to Tomcat configuration files (server.xml, context.xml, tomcat-users.xml, web.xml) containing sensitive data, and network indicators of cleartext protocol usage to Tomcat listener ports.

MITRE ATT&CK

Tactic
Credential Access Collection Initial Access

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule cve_2026_34486_tomcat_missing_encryption {
  meta:
    description = "Detects access to sensitive Tomcat config files or cleartext HTTP to Tomcat ports, consistent with CVE-2026-34486"
    severity = "HIGH"
  events:
    $file.metadata.event_type = "FILE_OPEN"
    $file.target.file.full_path = /tomcat-users\.xml|server\.xml|context\.xml|web\.xml/ nocase
    $net.metadata.event_type = "NETWORK_HTTP"
    $net.target.port = 8080 or $net.target.port = 8009 or $net.target.port = 80
    $net.network.tls.established = false
  match:
    $file.principal.hostname = $net.principal.hostname over 10m
  condition:
    $file or $net
}
high severity medium confidence

Chronicle YARA-L rule correlating sensitive Tomcat configuration file access with cleartext HTTP network sessions on the same host, indicating potential CVE-2026-34486 exploitation or data exposure.

Data Sources

Chronicle EDR File EventsChronicle Network Events

Required Tables

FILE_OPENNETWORK_HTTP

False Positives & Tuning

  • Config management agents legitimately reading files as part of scheduled compliance checks
  • Internal segmented networks where cleartext HTTP is an accepted risk behind other controls
  • Duplicate detections from multiple EDR sensors on the same host

Other platforms for CVE-2026-34486


Testing Methodology

Validate this detection against 4 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.

  1. Test 1Simulate cleartext credential exposure in tomcat-users.xml

    Expected signal: File creation and read events for tomcat-users.xml containing plaintext credential strings

  2. Test 2Simulate cleartext HTTP request to Tomcat port

    Expected signal: Network connection event to destination port 8080 using HTTP protocol without TLS

  3. Test 3Simulate access to Tomcat server.xml configuration file

    Expected signal: DeviceProcessEvents/DeviceFileEvents showing PowerShell reading server.xml with connector definitions

  4. Test 4Simulate AJP cleartext connector probe

    Expected signal: Network connection attempt logged to destination port 8009 (AJP) without TLS negotiation

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-34486 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections