Threat actors are chaining a fresh authentication bypass in Ivanti Connect Secure into credential theft and data theft, and the Cybersecurity and Infrastructure Security Agency is telling every organization still running vulnerable builds to patch first and assume compromise if the box sat on the internet through October.
CVE-2026-104935 landed on CISA’s Known Exploited Vulnerabilities list on October 13 after Ivanti disclosed remote, unauthenticated command execution against multiple release trains. Affected versions include 25.1.1.1 and earlier on the 25.x line, 25.1.2.2 and earlier on supported branches, and 22.8R2.4 and earlier on the aging 22.8 train that reaches end of life on January 31, 2027.
Immediate patch path
Ivanti’s advisory points administrators to the latest fixed builds and to the 25.x upgrade compatibility guide for hardware and virtual appliances. Cloud and virtual deployments should rebuild the instance on a patched image rather than layering a hotfix on a VM that may already be compromised.
Limit external exposure while you work: VPN concentrators and remote-access gateways are exactly the sort of edge gear that nation-state crews prioritize because security teams rarely watch them as closely as identity providers.
When you need the factory reset playbook
If forensics or log gaps suggest exploitation, CISA publishes a recovery sequence that starts with a configuration backup, continues with factory reset or rebuild on current code, restores configuration from that backup, and ends with password resets for every account class — domain, local, and appliance admin — plus revocation of stored certificates, API keys, and license-server credentials.
Memory forensics may be the only way to confirm attacker commands that never touched disk. Treat any Connect Secure appliance that accepted anonymous sessions in October as a pivot point until proven otherwise, and extend hunts to identity systems those VPNs fed.
Who is exposed
Connect Secure sits in small and mid-sized enterprises, universities, and municipal networks that cannot afford a second remote-access stack. Home users are not the target; employees whose employers rely on the appliance for vendor access are.
Share the CISA alert with whoever owns change control this weekend. The KEV deadline for federal civilian agencies is binding; private networks that skip the catalog anyway inherit the same attackers.
Document the patch window in your change ticket with the CVE number, the build you upgraded to, and whether you performed a factory reset. Auditors and cyber insurers increasingly ask for that paper trail after high-profile VPN flaws.
If your organization lacks memory-forensics capacity, contract a firm that has handled Ivanti incidents before you restore production VPN access. Skipping that step saves a weekend and costs a quarter.
Lessons from prior Ivanti waves
Security vendors tracked similar authentication bypass chains on Ivanti Pulse and Connect Secure appliances in 2023 and 2024, and many enterprises assumed migration to the 25.x train closed the chapter. CVE-2026-104935 shows that assumption was premature for teams that patched late or kept legacy 22.8 hardware running past vendor sunset warnings.
Identity providers fed by VPN logs should rotate SAML metadata and review conditional access rules for impossible-travel alerts starting Monday. Attackers who cleared VPN authentication in October may already sit on workstation sessions that never touched the Ivanti box again.
Board members should ask for a one-page summary: count of affected appliances, patch completion percentage, and whether factory resets occurred. Regulators and cyber insurers will want that timeline if customer data later appears on leak sites.
None of the steps above replace a documented incident response plan; they buy time while executives decide whether to notify customers under state breach rules.
