CVE Tools

CVE-2026-104935

Exploited in the wild. In CISA KEV since 2026‑10‑13. Fixed versions are out.

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • Ivanti Connect SecureFixed builds25.1.3.0, 25.1.3.1, 22.8R2.5, 22.7R2.14Stated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check your Ivanti Connect Secure version — if it is earlier than 25.1.3.0, you are affected (versions 22.7R2.14 and earlier are not affected).
  2. Review Ivanti's advisory for your specific branch at the vendor link below.
  3. Upgrade to one of the fixed versions: 25.1.3.0, 25.1.3.1, 25.1.1.2, or 22.8R2.5 (if on the 22.x branch, use 22.8R2.5).
  4. If you cannot patch immediately, follow Ivanti's mitigation steps and consider temporarily taking the device offline from the internet.
  5. Confirm with your IT provider that the fix is applied by October 16, 2026, the deadline set by the US government's cybersecurity agency for this flaw.

Coverage timeline

2 publishers
  1. Threat actor UTA0576 exploited a chain of three zero-day vulnerabilities in Ivanti Connect Secure to gain root access on patched appliances, performing credential theft and reconnaissance before detection.

    ·SecurityWeek summary
  2. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened. 1 further article named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

Authentication bypass by spoofing in ICS before version 25.1.3.0 allows a remote unauthenticated attacker to execute arbitrary commands. This does not impact ICS version 22.7R2.14 or prior.

In plain language

Written by AI from the record

Ivanti Connect Secure VPN devices before version 25.1.3.0 have a flaw that lets an attacker break in without a password and run commands on the device, and attackers are already doing this — if you use this VPN, treat it as urgent.

CWE-290 authentication-bypass-by-spoofing in Ivanti Connect Secure before 25.1.3.0 lets an unauthenticated remote attacker impersonate a trusted entity to achieve arbitrary command execution; CISA KEV confirms active exploitation.

If you're affected

  • Full VPN appliance takeover
  • Network-wide intrusion point
  • Customer and employee data exposure
  • Operational disruption from remote access outage
  • Ransomware entry point

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

CISA KEV
CISA KEV

Listed as exploited in the wild since 2026-10-13.

US federal agencies must remediate by 2026-10-16.

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

No EPSS score yet. New CVEs are usually scored within a few days.

Lifecycle

8 events over 1 day, from the signal feeds we watch.

  1. Nuclei check added
  2. Added to CISA KEVpatch available, published, weakness classified, att&ck mapped, record updated, record updated

Affected products

And 1 more affected product. See all after sign-in

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L

Scored 8.6 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Connect Secure, not every advisory. This one: actively exploited.