CVE-2026-1340 Google Chronicle · YARA-L

Detect Ivanti EPMM Code Injection Exploitation (CVE-2026-1340) in Google Chronicle

Detects exploitation attempts targeting CVE-2026-1340, a code injection vulnerability (CWE-94) in Ivanti Endpoint Manager Mobile (EPMM). This vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog and allows remote attackers to inject and execute arbitrary code via the EPMM management interface. Successful exploitation may lead to full device management compromise, lateral movement, and data exfiltration from enrolled mobile devices.

MITRE ATT&CK

Tactic
Initial Access Execution Lateral Movement

YARA-L Detection Query

Google Chronicle (YARA-L)
yaral
rule ivanti_epmm_code_injection_cve_2026_1340 {
  meta:
    author = "df00tech Detection Engineering"
    description = "Detects code injection exploitation attempts against Ivanti EPMM (CVE-2026-1340)"
    severity = "CRITICAL"
    priority = "HIGH"
    reference = "https://nvd.nist.gov/vuln/detail/CVE-2026-1340"
    cve = "CVE-2026-1340"
  events:
    $http.metadata.event_type = "NETWORK_HTTP"
    $http.target.url.path = /\/(mifs|mi|api\/v[12])\//
    (
      $http.target.url.path = /eval\(|exec\(|Runtime\.exec|ProcessBuilder|groovy|ognl|ScriptEngine|javax\.script|\$\{|#\{/
      or $http.target.url.query = /eval\(|exec\(|Runtime\.exec|ProcessBuilder|groovy|ognl|ScriptEngine|\$\{|#\{/
    )
    $http.network.http.response_code != 400
    $http.network.http.response_code != 403
  condition:
    $http
}
critical severity medium confidence

Chronicle YARA-L rule detecting HTTP requests to Ivanti EPMM paths containing code injection payload signatures, filtering out blocked requests to reduce noise.

Data Sources

Chronicle UDM eventsWeb proxy logsNetwork telemetry

Required Tables

UDM events (NETWORK_HTTP type)

False Positives & Tuning

  • EPMM scripting features or plugin APIs that legitimately accept code-like input
  • Authorized penetration testing or red team operations targeting EPMM infrastructure
  • Third-party MDM integrations that pass template expressions through EPMM APIs
  • URL-encoded payloads from legitimate MDM clients that contain characters triggering injection patterns

Other platforms for CVE-2026-1340


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.

  1. Test 1EPMM API Endpoint Code Injection Pattern Probe

    Expected signal: Web server access logs will show POST requests to /mifs/j_spring_security_check and GET requests to /api/v1/configuration/users with URL-encoded injection patterns. Network security appliances should log the requests with high-severity signatures. Host-based EDR should not show process anomalies for a non-successful probe.

  2. Test 2Simulate Java Process Spawning Shell After EPMM Exploitation

    Expected signal: Process creation events showing java spawning /bin/sh as a child process. EDR telemetry should capture the full process tree: [parent] -> java -> sh -> id/hostname/whoami. Command line arguments visible in process creation logs.

  3. Test 3EPMM Reconnaissance — Unauthenticated API Enumeration

    Expected signal: Web access logs showing sequential requests from a single IP to multiple EPMM administrative paths within a short time window. Firewall or IDS/IPS logs may flag the scanning pattern. HTTP response codes (200, 302, 401, 403) visible in logs.

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections