Two Ivanti Connect Secure zero-days, CVE-2026-111357 and CVE-2026-118527, joined the CISA Known Exploited Vulnerabilities catalog on October 30, 2026. They chain with an earlier authentication bypass to reach root on the appliance. Install the October 29 builds on every appliance, then hunt for compromise, because a patch alone does not close this one.
What Are the New Ivanti Connect Secure KEV Entries?
CISA added two flaws to its catalog. First, CVE-2026-111357 is a missing authentication for a critical function that lets a local, authenticated attacker escalate privileges to root. Second, CVE-2026-118527 is a predictable identifier flaw that lets a remote, authenticated attacker write a file with attacker controlled content to a known location on disk. Together, they extend an attack chain that defenders have tracked since early October.
How Does the Ivanti Connect Secure Zero-Day Chain Work?
The two new flaws do not stand alone. Instead, they chain with CVE-2026-104935, the authentication bypass that CISA listed on October 13. An attacker bypasses authentication, escalates to root with CVE-2026-111357, and uses CVE-2026-118527 to place a file on disk. After that, the attacker steals the appliance’s LDAP credentials and moves into the wider network.
In addition, reporting on the incident describes an actor tracked as UTA0576, with exploitation observed from October 3 against an appliance that was fully patched at 22.8R2.4. After gaining root, the actor took the LDAP bind credentials and moved into Active Directory through Kerberoasting and password spraying.
Which Ivanti Connect Secure Versions Should You Patch?
However, the uncomfortable detail is that a patched appliance still fell. Attackers compromised units running 22.8R2.4 even though that build was fully patched at the time, so an earlier fix was not enough. Therefore, install the October 29, 2026 builds from the vendor advisory on every Ivanti Connect Secure appliance, including the ones you patched on October 13. The table below collects the confirmed facts.
| Item | Detail |
|---|---|
| CVEs | CVE-2026-111357 and CVE-2026-118527 |
| CVE-2026-111357 | Missing authentication, local escalation to root |
| CVE-2026-118527 | Predictable identifier, authenticated file write to a known path |
| Chained with | CVE-2026-104935, authentication bypass, on KEV since October 13 |
| Affected | Ivanti Connect Secure appliances, including 22.8R2.4 |
| Fix | Install the October 29, 2026 builds from Ivanti’s advisory |
| CISA KEV added | October 30, 2026, catalog version 2026.10.30 |
| Federal deadlines | CVE-2026-111357 by November 2, CVE-2026-118527 by November 13 |
| Threat actor | Tracked as UTA0576, exploitation observed from October 3 |
You can confirm the fixed build in the official Ivanti October 2026 security update, and the catalog entries in the CISA Known Exploited Vulnerabilities catalog.
How Strong Is the Evidence Behind the Ivanti Connect Secure Chain?
We separate confirmed facts from single reports, so you can judge the risk yourself.
- Confirmed by CISA: both CVEs on the KEV catalog, the October 30 addition, the catalog version 2026.10.30, and the federal remediation requirement
- Confirmed by Ivanti: the affected product and the October 29 builds as the fix
- Reported, not confirmed by us: the UTA0576 attribution, the October 3 start, the compromise of a fully patched 22.8R2.4 appliance, and the LDAP and Active Directory post exploitation
- Still open: public CVSS scores for both CVEs, and an exact fixed build number beyond the October 29 builds. Confirm the deadlines against the catalog entry
How Do You Detect and Respond on Ivanti Connect Secure?
Still, patching is step one, not the finish line. The vendor’s Integrity Checker Tool may not detect this compromise, so assume a patched box can still be dirty. Work through these checks on every Ivanti Connect Secure appliance that faced the internet.
- Forensics first: run network and memory forensics rather than trusting the Integrity Checker Tool alone
- Rotate credentials: reset the LDAP bind account and every credential it could read, because root access exposes them all
- Hunt Active Directory: look for Kerberoasting and password spraying that started on or after early October
- Check the timeline: treat any appliance exposed before the October 29 builds as suspect, even one patched on October 13
- Rebuild when unsure: if you cannot rule out compromise, rebuild the appliance from a known good image and rotate secrets
What Does the Latest CISA KEV Snapshot Show?
As of the November 1, 2026 monitoring window, the CISA KEV catalog remains at version 2026.10.30, released October 30 at 17:02 UTC, with 1,766 vulnerabilities. No new entry joined the catalog in this window, so the most recent additions are still the two Ivanti Connect Secure CVEs. A quiet day on the catalog is not a quiet day for defenders, because the Ivanti deadlines fall inside it.
What Should Your Team Do About Ivanti Connect Secure Now?
Edge appliances concentrate access, so attackers reach them first. Our 2026 Mid Year Threat Pattern Report found that attackers weaponized eight of eleven zero days, or 73 percent, within 72 hours of disclosure, and this chain fits that pattern exactly. Therefore, move on the October 29 builds today and treat the forensic work as part of the same task.
Above all, prove the appliance is clean rather than assume it. Our team runs penetration testing and vulnerability assessments that show what an attacker can reach through your Ivanti Connect Secure gateway, and our PTaaS platform keeps that testing running between audits.
Key Takeaways
- CVE-2026-111357 and CVE-2026-118527 are the latest Ivanti Connect Secure additions to the CISA KEV catalog, added October 30, 2026
- The two flaws chain with CVE-2026-104935 to bypass authentication, reach root, and write a file to disk
- A fully patched 22.8R2.4 appliance was still compromised, so install the October 29 builds on every appliance
- The Integrity Checker Tool may miss this compromise, so run network and memory forensics and rotate the LDAP bind account
- As of November 1, 2026, the KEV catalog holds 1,766 vulnerabilities at version 2026.10.30, with no new entry in the window
Frequently Asked Questions About the Ivanti Connect Secure Zero-Days
What are the new Ivanti Connect Secure KEV entries?
They are CVE-2026-111357 and CVE-2026-118527. Specifically, CISA added both to its Known Exploited Vulnerabilities catalog on October 30, 2026, and they chain with the earlier authentication bypass CVE-2026-104935.
Which Ivanti Connect Secure versions should you patch?
Connect Secure appliances across the chain, including units running 22.8R2.4, which attackers compromised despite that build being fully patched at the time. Install the October 29, 2026 builds from Ivanti’s advisory on every appliance.
Are attackers exploiting the Ivanti Connect Secure flaws?
Yes. CISA lists both on the KEV catalog, and incident responders reported exploitation of the chain from early October against a fully patched appliance.
What are the federal deadlines for the Ivanti Connect Secure CVEs?
Published reporting puts the deadline for CVE-2026-111357 at November 2, 2026 and CVE-2026-118527 at November 13, 2026. However, confirm the dates against the CISA KEV catalog entry.
Does patching Ivanti Connect Secure close the incident?
Not on its own. The Integrity Checker Tool may miss this compromise, so pair the patch with network and memory forensics, and rotate the LDAP bind account and any credentials it could read.
Did any new vulnerability join the KEV catalog today?
No. As of the November 1, 2026 window, the catalog remains version 2026.10.30 with 1,766 vulnerabilities, and the most recent additions are still the two Ivanti Connect Secure CVEs.

