Exploited CVEs / Ivanti / CVE-2026-118527

CVE-2026-118527

Ivanti Connect Secure Generation of Predictable Numbers or Identifiers Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies must remediate by 2026-11-13; 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.

CISA required action Official fix for CVE-2026-118527 Admin questions

Risk summary

UnratedCISA KEV

CVSS v3 base

Not scored

EPSS exploit probability

Unrated

Severity

2026-10-30

Added to KEV

2026-11-13

CISA due date

Actively exploited Ivanti Connect Secure vulnerability. Added to the CISA KEV catalog 2026-10-30.

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-11-13; treat it as your outer bound. Patch now and verify deployment on every exposed device.

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

Senserva AI Opinion and rich prompt for CVE-2026-118527

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

I run IT security. Facts for CVE-2026-118527, an actively exploited vulnerability (source: https://senserva.com/cve/CVE-2026-118527.html, data from CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- CVE-2026-118527: Ivanti Connect Secure Generation of Predictable Numbers or Identifiers Vulnerability
- Affected: Ivanti Connect Secure
- Severity: Unrated
- Added to CISA KEV: 2026-10-30; federal remediation due 2026-11-13
- Ransomware-linked: no
- CISA 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 dis...
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) The fastest safe path to remediation. 4) How to check whether my environment is exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for CVE-2026-118527

Published: 2026-10-30
Last revised: 2026-10-30
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.

CISA required action

Federal remediation due date: 2026-11-13.

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-118527

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

Ivanti Security Advisories CISA KEV entry

Common questions about CVE-2026-118527

Is CVE-2026-118527 actively exploited?

Yes. CVE-2026-118527 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-10-30, which means exploitation in the wild has been confirmed, not predicted.

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

CISA set the federal remediation due date at 2026-11-13. 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-118527?

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-118527?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-118527'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).

Scope and sources

More exploited Ivanti CVEs: CVE-2026-111357 CVE-2026-104935 CVE-2026-10520 CVE-2026-6973 CVE-2026-1340 CVE-2026-1603 CVE-2026-1281 CVE-2025-4427
All Ivanti exploited CVEs on one page: Ivanti vulnerabilities actively exploited.
Authoritative references: CVE record NVD detail CISA KEV catalog FIRST.org EPSS

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