VULNpocalypse

CVE-2026-1340: Ivanti Endpoint Manager Mobile (EPMM) Code Injection Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

A code injection in Ivanti Endpoint Manager Mobile allowing attackers to achieve unauthenticated remote code execution.

Description quoted from the CVE record (assigned by ivanti, published 2026-01-29).

Weakness: CWE-94 Improper Control of Generation of Code (‘Code Injection’)

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: total.

On CISA KEV since
2026-04-08
US federal deadline
2026-04-11
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-01123, CNNVD-202601-4863, CNVD-2026-39108, EUVD-2026-4936, GHSA-wv3p-w5rj-f5p6

VEDAS cluster: VEDAS:BARKLETT

Exploit Observer links 7 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (7)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (4)

Vulnerability databases and vendor advisories (8)

Catalogue entries, not exploit evidence.

128 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.986
very likely to be attacked soon
VEDAS
0.984
strong exploit evidence
On CISA KEV
Yes, since 2026-04-08
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.1Added to CISA KEV 2026-04-08CVE-2026-1340 EPSS over time2026-022026-11-01
VEDAS (exploit evidence)
10No cve-scores data 2026-02-22 to 2026-08-08no data0.9Added to CISA KEV 2026-04-08CVE-2026-1340 VEDAS over time2026-022026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.

Who is affected

ProductAffectedNot affected
Ivanti Endpoint Manager MobileNot stated12.x.1.x RPM is not affected; 12.x.0.x RPM is not affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: ivanti endpoint_manager_mobile, ivanti ivanti_endpoint_manager_mobile.

How to fix it

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.

Vendor guidance:

How to detect it

Nuclei template (active check)

Ivanti - Code Injection

A code injection in Ivanti Endpoint Manager Mobile allowing attackers to achieve unauthenticated remote code execution.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (GET /mifs/user/login.jsp); it decides using dsl, regex matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-1340.yaml
Show the template (51 lines)
yaml
id: CVE-2026-1340

info:
  name: "Ivanti - Code Injection"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    A code injection in Ivanti Endpoint Manager Mobile allowing attackers to achieve unauthenticated remote code
    execution.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-1340&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=ivanti&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
    cvss-score: 9.8
    cve-id: CVE-2026-1340
    cwe-id: CWE-94
  metadata:
    verified: false
  tags: cve,cve2026,ivanti,epmm,mobileiron,rce,kev,passive,vkev
http:
  - raw:
      - |
        GET /mifs/user/login.jsp HTTP/1.1
        Host: {{Hostname}}

    redirects: true
    max-redirects: 3

    matchers:
      - type: dsl
        dsl:
          - 'status_code == 200'
          - 'contains(body, "Ivanti")'
          - 'compare_versions(version, "< 12.8.0")'
        condition: and

    extractors:
      - type: regex
        name: version
        part: body
        group: 1
        internal: true
        regex:
          - 'ui\.login\.css\?([0-9]+\.[0-9]+(?:\.[0-9]+)?)'

      - type: regex
        part: body
        group: 1
        regex:
          - 'ui\.login\.css\?([0-9]+\.[0-9]+(?:\.[0-9]+)?)'

CVE-2026-1340.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-1340 Ivanti - Code Injection. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-1340 Ivanti - Code Injection"; flow:established,to_server; http.uri; content:"/mifs/user/login.jsp"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-1340; reference:url,https://www.exploit.observer/?keyword=CVE-2026-1340&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=ivanti&match=exact; sid:1010074; rev:1;)

CVE-2026-1340.rules on GitHub

Advisories on this CVE

References

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.