NETWORK INCIDENTS

Exploited now

Remediation guide
Ivanti · Connect Secure

CVE-2026-104935

Security Advisory Ivanti Connect Secure (CVE-2026-104935)

CISA KEV
Known exploitedadded 13 Oct 2026; US federal deadline 16 Oct 2026
Exploit likelihood
89%100th percentile · FIRST EPSS, 2026-11-15
Severity
8.6 HighCVSS 3.0, Ivanti
Last verified
31 Oct 2026against the sources below

1In plain language

An authentication bypass by spoofing in Ivanti Connect Secure (ICS) before version 25.1.3.0 lets a remote attacker who hasn't logged in run arbitrary commands. Ivanti's version table also lists 25.1.1.2 and 22.8R2.5 as fixing this CVE (see Fix for why those aren't enough).

Ivanti is aware of exploitation in the wild affecting a limited number of customers, when this CVE was chained with two others, CVE-2026-111357 (a local privilege escalation) and CVE-2026-118527 (file upload to a known location). CISA lists it as known to be exploited.

Ivanti's 29 October update added fixed versions for the two chained CVEs.

Patch for all three, not just this one: the exploitation Ivanti describes chains them. our analysis

2Am I affected?

For this CVE, Ivanti lists as affected: 25.1.1.1 and prior, 25.1.2.2 and prior, and 22.8R2.4 and prior. It does not impact ICS 22.7R2.14 or prior.

For the two chained CVEs, Ivanti lists 25.1.1.2 and prior and 22.8R2.5 and prior as affected.

Affected releases are summarised by release train in the Fix table.

Check your version

A command to show the running ICS version: Not stated by vendor.

3Fix

If you updated to 25.1.1.2 or 22.8R2.5 for this CVE, update again: Ivanti lists those versions as affected by the two chained CVEs, which are fixed in 25.1.1.3 and 22.8R2.6. Ivanti shipped this CVE's fix first, without waiting for the fix for the privilege escalation discovered later.

Ivanti's solution is to update to one of the resolved versions of code. Downloads are in the Ivanti License System (ILS). How to access ILS downloads ↗

Moving to 25.1.3.0 needs the new platform (ISA4500, ISA6500 or ISA8500): new physical servers for hardware, or new virtual or cloud devices built from the 25.1.3.0 template. Ivanti's migration guide covers it. Upgrade and migration guide ↗

Updating closes the hole but doesn't remove an attacker who is already in: run the checks under Was I hit? too. our analysis

RunningAffectedWhat Ivanti says to do
ICS 22.7.X and lowerNot affected by this CVE (22.7R2.14 or prior)Ivanti says 22.7.X and lower don't contain this vulnerability. The advisory doesn't say whether 22.7 is affected by the two chained CVEs. 22.7 reaches end of life on January 31, 2027: plan to move to 25.1 before then.
ICS 22.8.X22.8R2.4 and prior (this CVE); 22.8R2.5 and prior (the chained CVEs)Update to 25.1.1.3 or later. If you can't move to 25.1.1.3 yet, 22.8R2.6 resolves all vulnerabilities in this disclosure. Ivanti calls 22.8 a temporary bridge from 22.7 to 25.1; it reaches end of life on January 31, 2027.
ICS 25.1.1.x (ISA6000 or ISA8000)25.1.1.1 and prior (this CVE); 25.1.1.2 and prior (the chained CVEs)Update to 25.1.1.3, which resolves all vulnerabilities in this disclosure.
ICS 25.1.2.x25.1.2.2 and priorIvanti's Solution section doesn't cover 25.1.2.x. Its version table lists 25.1.2.2 and prior as affected, with 25.1.3.0 and 25.1.3.1 among the resolved versions. Migrating to 25.1.3.0 requires the ISA4500, ISA6500 or ISA8500 platform. The advisory doesn't say whether 25.1.2.x is affected by the two chained CVEs.The pairing of 25.1.2.2 with 25.1.3.0 / 25.1.3.1 is our reading of Ivanti's table, which lists the versions in one cell each. our analysis
ICS 25.1.3.0 or later (ISA4500, ISA6500 or ISA8500)Not affected by this CVENo fix needed for this CVE. Ivanti always recommends the latest version.

4Can't patch tonight?

Workarounds or mitigations: Not stated by vendor.

5Was I hit?

Ivanti says only limited indicators of compromise are available. Its advice: review the indicators in Volexity's blog post, and run the Integrity Checker Tool regularly. Volexity's blog post ↗

If you suspect exploitation, Ivanti says to follow its recovery steps. Ivanti's recovery steps ↗

Ivanti says indicators are limited: treat a clean Integrity Checker run as one check, not proof the appliance is clean. our analysis

CISA's catalog flags this CVE for forensic triage, and its required action points to CISA's BOD 26-04 guidance and its Forensics Triage Requirements.

6Sources

Summary of public vendor guidance. Verify against the vendor advisory before acting.

See CVE-2026-104935 in the exploited-now list (exploit likelihood, CISA's description, deadline).

More Ivanti guides