Skip to main content
CVE-2026-118527VulnerabilityPublished

Ivanti Connect Secure · Use of Predictable Filenames

Affects Ivanti Connect SecureSource GCVE Database

0
Compare
Authoritative record:CVE-2026-118527· Medium 4.3

Exploited in the wild · KEV due 13 Nov 2026 : apply the vendor's fix or mitigations to Ivanti Connect Secure now.

Data as of 3 Nov 2026, 16:45 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (ivanti)CVSS 3.14.3
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: evidence found.

    Listed in CISA KEV 4 days before disclosure

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Ivanti

    , 6 days before disclosure

  2. , 4 days before disclosure

  3. CVE published

    on cve.org

    , t = 0

  4. In Threat Radar

    record ingested

    , 5 minutes after disclosure

  5. KEV remediation due

    US federal deadline

    , 10 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

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.

Affected software

ProductAffectedFixed in
IvantiConnect SecureAffected–Fixed in–

Check the firmware or software version for Ivanti Connect Secure in the device's admin interface against the vendor advisory.

Description

Ivanti Connect Secure versions prior to 25.1.1.3 and 22.8R2.6 contain a vulnerability where predictable filenames allow a remote authenticated attacker to upload files with attacker-controlled content to a known disk location.

References

Community reviews

Loading reviews…