~/exploited / cve-2026-104935
CVE-2026-104935: Ivanti Connect Secure
According to CISA this vulnerability is already used in attacks (added on 13 October 2026).
Key facts
| CVE | CVE-2026-104935 |
|---|---|
| Vendor | Ivanti — Connect Secure |
| Vulnerability | Ivanti Connect Secure Authentication Bypass by Spoofing Vulnerability |
| Added | 13 October 2026 |
| Deadline (US agencies) | 16 October 2026 |
| Ransomware campaigns | unknown |
Technical data (NVD, FIRST EPSS)
| CVSS base score | 8.6 (high) · CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:LAttack over the network, complexity: low, privileges: none needed, user interaction: none |
|---|---|
| EPSS (exploitation probability) | Probability of exploitation in the next 30 days: 88.94%. Higher than 99.8% of all scored vulnerabilities (as of 18 November 2026). A high value means attacks are very likely and often already widespread. |
| Weakness type (CWE) | CWE-290 |
| Affected versions | connect secure: >= 25.1.0.0, < 25.1.1.2 connect secure: >= 25.1.2.0, < 25.1.3.0 connect secure 22.8 |
Description (NVD)
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.
Patches and vendor advisories
Description (CISA)
Ivanti Connect Secure contains an authentication bypass by spoofing vulnerability that allows a remote unauthenticated attacker to execute arbitrary commands.
Required action (CISA)
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.
What admins should do now
- Affected? Check whether Ivanti Connect Secure is in use and which version runs (package manager, admin UI,
--version). - Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
- Review logs back to 13 October 2026: unusual logins, new files, unexpected processes, outbound connections.
- If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.
The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.
Sources
New articles by e-mail
One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).