Ivanti Connect Secure

Ivanti VPN Flaw Lets Attackers Forge Trust, Not Just Steal It

Ivanti VPN Flaw Lets Attackers Forge Trust, Not Just Steal It

A newly catalogued flaw in Ivanti Connect Secure allows an attacker with no credentials and no prior access to execute commands on the appliance simply by forging the signal the device uses to decide who counts as authenticated. The vulnerability, tracked as CVE-2026-104935, has been added to the Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalog, and federal civilian agencies have been given a 72-hour window to act - one of the tightest deadlines attached to a VPN flaw in recent memory.

A Lock That Opens for a Forged Key

The vulnerability is classified under CWE-290, authentication bypass by spoofing. That classification matters because it describes a specific kind of failure. This is not a missing login screen, and it is not a door left open by a misconfigured permission. The authentication mechanism is present and functioning as designed. The problem is that the appliance accepts a forged identity claim as genuine. An attacker does not need a password, a token, or a session cookie - only the ability to make the device believe a false signal is true.

That distinction shapes the entire risk profile. The flaw carries a CVSS 3.1 base score of 8.6, driven by a vector that requires no privileges and no user interaction, exploitable remotely over the network. The impact leans heavily toward confidentiality, rated High, while integrity and availability are both rated Low. In plain terms, the likely objective of an intruder exploiting this flaw is reading what the appliance can see - session data, configuration details, internal network paths - rather than destroying or altering it outright. That is the signature of an attack aimed at the trust boundary itself, not the service sitting behind it.

Why the September Bulletin Is Not Enough

Organizations that patched against Ivanti's earlier, batched September advisory may reasonably believe they addressed their exposure. They did not address this one. CVE-2026-104935 affects all Connect Secure versions prior to 25.1.3.0; only 22.7R2.14 and earlier builds fall outside the affected range entirely. There is no workaround. Ivanti has published three fixed versions - 25.1.3.0, 25.1.3.1, and 22.8R2.5 - and applying one of them is the only remediation path.

The KEV listing also carries a forensics triage requirement, a detail that deserves attention on its own. CISA does not routinely demand forensic review for every cataloged vulnerability; it does so when there is reason to believe exploitation has already produced artifacts worth investigating. Paired with the compressed deadline, that requirement signals this is being treated as an active incident pattern, not a precautionary patch cycle.

A Familiar Shape Across Remote-Access Infrastructure

This flaw fits a pattern that has recurred across perimeter security products: a control plane ships with an authentication design that looks sound until an external researcher or an attacker demonstrates that the trust signal can be manufactured. Similar dynamics have played out elsewhere - pre-authentication request forgery in VPN concentrators, identity-federation systems requiring hardened access controls after disclosure. What distinguishes the Ivanti case is that the compromised layer is the VPN perimeter itself, the exact component organizations rely on to establish that a remote connection is legitimate before anything else happens.

For defenders, the practical response is mechanical rather than strategic: inventory every Connect Secure deployment, check the running version against the unaffected range, schedule the upgrade to 25.1.3.0 or later without delay, and treat any internet-facing appliance that remained unpatched during the exposure window as a candidate for forensic review rather than a routine update. The agency deadline falls on Thursday. The authentication on these devices was never absent - it was simply possible to counterfeit, and that gap is what the firmware upgrade is built to close.