Exploited CVEs / Ivanti / CVE-2026-104935

CVE-2026-104935

Ivanti Connect Secure Authentication Bypass by Spoofing Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies must remediate by 2026-10-16; treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Ivanti Security Advisories, linked below.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Risk summary

In the top 10 of the Senserva CVE Ranking (as of 2026-10-15)
HighCISA KEV
8.6
CVSS v3 base
26%
EPSS exploit probability
High
Severity
2026-10-13
Added to KEV
2026-10-16
CISA due date

Actively exploited Ivanti Connect Secure vulnerability, High severity, CVSS v3 8.6. Added to the CISA KEV catalog 2026-10-13.

CISA required actionOfficial fix for CVE-2026-104935What the press saysAdmin questions#5 hottest CVE right now
Senserva AI Opinion and rich prompt for CVE-2026-104935

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
The fix ships from the vendor: Ivanti Security Advisories.
Do this now: Federal remediation deadline 2026-10-16; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated October 13, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-104935

Published
2026-10-13
Last revised
2026-10-13
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when

CISA confirmed active exploitation of CVE-2026-104935 on 2026-10-13, and its EPSS exploit probability moved from 0.0% to 26% by 2026-10-14.

0%25%50%75%100%CISA KEVCISA KEV on 2026-10-132026-10-13: EPSS 0.0%2026-10-13: EPSS 0.0%2026-10-14: EPSS 26%2026-10-14: EPSS 26%EPSS 26%2026-10-132026-10-14

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-10-13 CVSS 0.0 to 8.6; EPSS first scored at 0.0%; added to the CISA KEV catalog by CISA
  • 2026-10-14 EPSS 0.0% to 26.0%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

What the press says about CVE-2026-104935

Trusted-source coverage, pulled live from their own feeds.

“CISA Warns of Hackers Exploiting Ivanti Connect Secure Zero-Day to Steal Credentials” Cyber Security News, 2026-10-15
“Ivanti ICS Zero-Day Attacks Highlight Vendor Patching Hurdles” Dark Reading, 2026-10-14
“Ivanti Connect Secure zero-day exploited in the wild (CVE-2026-104935)” Rapid7, 2026-10-13

CISA required action

Federal remediation due date: 2026-10-16.

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.

Official fix for CVE-2026-104935

The authoritative fix and affected-version list are published by the vendor. Find the Connect Secure advisory on Ivanti Security Advisories.

Common questions about CVE-2026-104935

Is CVE-2026-104935 actively exploited?

Yes. CVE-2026-104935 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-10-13, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 26%.

What is the CISA deadline and required action for CVE-2026-104935?

CISA set the federal remediation due date at 2026-10-16. The verbatim required action: 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 fixes CVE-2026-104935?

The authoritative fix is in the vendor advisory: see Ivanti Security Advisories for the patched Connect Secure versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-104935?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-104935's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed daily (early morning US Central).

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
All information provided as is, without warranty; verify against the vendor advisory before acting. All information and usage is subject to the Senserva EULA. Data notice and terms.