CVE-2026-6973 Google Chronicle · YARA-L

Detect CVE-2026-6973: Ivanti EPMM Improper Input Validation Exploitation in Google Chronicle

Detects exploitation attempts targeting CVE-2026-6973, an improper input validation vulnerability in Ivanti Endpoint Manager Mobile (EPMM). This vulnerability is actively exploited in the wild (CISA KEV) and may allow attackers to bypass authentication or execute unauthorized actions against the EPMM management interface.

MITRE ATT&CK

Tactic
Initial Access Persistence Privilege Escalation

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule cve_2026_6973_ivanti_epmm_exploitation {
  meta:
    author = "df00tech Detection Engineering"
    description = "Detects exploitation attempts against Ivanti EPMM CVE-2026-6973"
    severity = "CRITICAL"
    priority = "HIGH"
    reference = "https://nvd.nist.gov/vuln/detail/CVE-2026-6973"

  events:
    $request.metadata.event_type = "NETWORK_HTTP"
    $request.principal.ip = $src_ip
    (
      $request.target.url.path = /\/mifs\// or
      $request.target.url.path = /\/api\/v[12]\// or
      $request.target.url.path = /\/admin\//
    )
    (
      $request.network.http.response_code = 400 or
      $request.network.http.response_code = 422 or
      $request.network.http.response_code = 500 or
      $request.target.url.query = /%00/ or
      $request.target.url.query = /%0[aAdD]/
    )

  match:
    $src_ip over 5m

  condition:
    #request > 5
}
critical severity medium confidence

Chronicle YARA-L rule detecting repeated malformed HTTP requests to Ivanti EPMM API endpoints within a 5-minute window, a pattern consistent with CVE-2026-6973 exploitation attempts.

Data Sources

Chronicle network telemetryWeb proxy logs ingested into Chronicle

Required Tables

network_http

False Positives & Tuning

  • Automated MDM management scripts generating high volumes of API requests
  • Security scanning tools authorized to test EPMM endpoints
  • Mobile device management bulk operations during peak enrollment periods
  • Misconfigured API clients repeatedly submitting invalid requests

Other platforms for CVE-2026-6973


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 1CVE-2026-6973 EPMM Input Validation Probe — Null Byte Injection

    Expected signal: HTTP 400 or 422 responses from EPMM server for null-byte payloads; web server access log entries with %00 in the URL; WAF alert if WAF is present

  2. Test 2CVE-2026-6973 EPMM API Endpoint Fuzzing — Oversized Input

    Expected signal: HTTP 400 or 500 response; web server log entry with large Content-Length header; potential application error log entry on EPMM server

  3. Test 3CVE-2026-6973 EPMM Admin API Unauthorized Access Attempt — CRLF Injection

    Expected signal: HTTP 400/422 responses; EPMM access log entries with CRLF sequences in headers; potential WAF alert on header injection attempt

  4. Test 4CVE-2026-6973 Post-Exploitation — EPMM Unauthorized Admin Enumeration

    Expected signal: Successful HTTP 200 responses to admin API endpoints (if token is valid); authentication/authorization log entries in EPMM audit log; network flow records showing enumeration pattern

Unlock Pro Content

Get the full detection package for CVE-2026-6973 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections