CVE-2026-104935 — ZERO-DAY — ACTIVELY EXPLOITED — CISA KEV

CVE-2026-104935: unauthenticated root on Ivanti — cybersecurity news

CVE-2026-104935 is a zero-day in Ivanti Connect Secure giving remote attackers unauthenticated command execution on the appliance. Threat actor UTA0576 chains it with an auth bypass and a privilege escalation to full root. CISA added it to the Known Exploited Vulnerabilities catalog on October 13 with a remediation deadline of October 16, 2026 (today). Paste your ICS version into this CVE checker for an instant verdict against the published version tables. Free, runs entirely in your browser, nothing is sent anywhere.

Key figure: CISA's Known Exploited Vulnerabilities catalog listed 1,748 entries as of October 16, 2026, every one confirmed exploited in the wild (CISA KEV catalog, version 2026.10.16).

The short version: Yes, you are at risk if your Ivanti Connect Secure runs 25.1.1.1, 25.1.2.2, or 22.8R2.4 or earlier. CVE-2026-104935 lets an unauthenticated attacker run commands on the VPN appliance, and the UTA0576 chain escalates that to root. It is actively exploited, memory-only (Ivanti's Integrity Checker Tool cannot see it), and CISA's patch deadline was October 16, 2026. The fix: 25.1.1.2, 25.1.3.0/25.1.3.1, or 22.8R2.5 depending on your branch.

Why is CVE-2026-104935 major cybersecurity news?

CVE-2026-104935 is major cybersecurity news because it allows unauthenticated remote-code execution as root on Ivanti Connect Secure VPN appliances — the front door to corporate networks. VPN flaws are prized by ransomware groups, and Ivanti devices have been mass-exploited before. Check your version with the tool above and patch immediately.

Affected vs fixed — version table by branch

Your branchVulnerablePatch to
25.1.1.x25.1.1.1 and earlier25.1.1.2
25.1.2.x25.1.2.2 and earlier25.1.3.0 / 25.1.3.1 (move to the 25.1.3 line)
25.1.3.x—25.1.3.0 / 25.1.3.1 (fixed)
22.8R2.x22.8R2.4 and earlier22.8R2.5
22.7 lineNot affected (22.7R2.14 and prior)

Source of these tables: the Ivanti advisory as reported October 2026. Always match the fix to your branch; cross-branch upgrades are not required.

Suspected compromise? Incident response steps

Hunt compromise indicators like these → BreachHunter

This page checked one CVE. BreachHunter hunts attacker infrastructure and compromise indicators — the footholds attackers keep after the initial exploit.

FROM INGENIOUS AI
Ingenious AI builds 11 AI security platforms — disclosure compliance, rogue-agent defense, breach hunting, agent oversight, and more.
All 11 platforms: DisclosureGuard  ·  ModelMinder  ·  TermsWatch  ·  Vibe-Code Audit  ·  Rogue-Agent Defense  ·  BreachHunter  ·  ChatBreaker  ·  Agent Flight Recorder  ·  Agent Auth Gateway  ·  DomainGuard  ·  ContentCraft AI
Our platforms are being upgraded and return November 1 — get early access now:
Get early access on WhatsApp →
Share this check: XLinkedInReddit

FAQ

What is CVE-2026-104935?

CVE-2026-104935 is a zero-day in Ivanti Connect Secure that allows remote, unauthenticated command execution on the VPN appliance. Threat actor UTA0576 chains it with an authentication bypass and a privilege escalation to reach unauthenticated root. Volexity reported the flaw; CISA added it to the Known Exploited Vulnerabilities catalog on October 13, 2026 with a remediation due date of October 16, 2026.

Which Ivanti Connect Secure versions are affected by CVE-2026-104935?

Affected: ICS 25.1.1.1 and earlier, 25.1.2.2 and earlier, and 22.8R2.4 and earlier. Not affected: the 22.7 line (22.7R2.14 and prior). If your version is on one of the affected lines below the fixed build, treat the appliance as compromised until proven otherwise.

What version fixes CVE-2026-104935?

Match the fixed build to your branch: 25.1.1.2 for the 25.1.1 line, 25.1.3.0 or 25.1.3.1 for the 25.1.3 line (the 25.1.2 line should upgrade to 25.1.3.0/25.1.3.1), and 22.8R2.5 for the 22.8 line. Ivanti has noted a separate privilege-escalation fix is still pending, so keep watching for further updates.

Why does Ivanti's Integrity Checker Tool not detect this attack?

The exploit chain runs entirely in memory, leaving nothing on disk for the Integrity Checker Tool to inspect. A clean integrity check therefore proves nothing here. If your appliance was internet-facing on a vulnerable build during the exploitation window, hunt with network and firewall logs from outside the appliance instead.

What should I do if my Ivanti Connect Secure was vulnerable during the attack window?

Per CISA: patch immediately, then treat a suspected appliance as compromised. Isolate it, perform a factory reset, rebuild from known-good configuration and media, rotate all credentials and certificates, review external logs for attacker activity, and report findings to CISA. Patching closes the hole but does not remove footholds an attacker already planted.

What is a CVE checker?

A CVE checker is a free tool that tells you whether your software is affected by a published CVE — a publicly known cybersecurity vulnerability. It compares your version or configuration against the official advisory and gives you a patched, vulnerable, or unknown verdict in about 30 seconds.

How do I check if my software has a CVE?

Find your exact version number, then compare it against the vendor's security advisory or the NVD entry for the CVE. The fastest way is a CVE checker built for that product: paste your version and get an instant verdict against the published version tables.

How do I know if I am affected by a CVE?

You are affected when you run a vulnerable version and the vulnerable component is reachable or enabled — for example, open sign-ups, an exposed management port, or a vulnerable app installed. A CVE checker gives you the version verdict in seconds; the advisory's conditions tell you whether that verdict means real exposure.

Related checks