Ivanti Connect Secure zero-day exploited in wild
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
CERT-FR warns a critical Ivanti Connect Secure vulnerability (CVE-2026-104935) is being actively exploited for remote code execution and privilege escalation.
CERT-FR issued an alert on a vulnerability in Ivanti Connect Secure (ICS) that Ivanti confirms is being actively exploited in the wild. The flaw, tracked as CVE-2026-104935, affects ICS versions 22.8Rx prior to 22.8R2.5, 25.1.1.x prior to 25.1.1.2, and 25.1.3.x prior to 25.1.3.1. Successful exploitation allows an attacker to bypass security policy, execute arbitrary code remotely, and escalate privileges — a combination that typically leads to full device compromise and lateral movement into internal networks via stored LDAP/Active Directory credentials.
Volexity published a companion report describing chained exploitation of ICS zero-days and associated indicators of compromise. CERT-FR's guidance emphasizes immediate isolation of affected appliances, forensic capture (disk/memory snapshots) before shutdown, log preservation, and use of Ivanti's Integrity Checker Tool (ICT) — noting that ICT requires physical access and may cause service interruption. CERT-FR explicitly notes awareness of lateral movement using compromised LDAP/AD secrets extracted from affected gateways.
Defenders running affected ICS versions should treat any potentially compromised appliance as fully compromised: reset LDAP/AD secrets, revoke and reissue all certificates (client/server/code-signing/TLS), reset admin passwords and API keys, reset local and service account credentials, revoke Kerberos tickets, and reset license server authentication. A factory reset is recommended but CERT-FR warns some threats may persist through reset in sensitive contexts. Organizations without an available patch should disconnect appliances from the Internet where possible and monitor LDAP/AD service account activity closely. This is a high-urgency event given confirmed active exploitation and known lateral movement using harvested credentials.
Mentioned in this report
Source reporting: https://www.cert.ssi.gouv.fr/alerte/CERTFR-2026-ALE-013
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs