CVE-2026-118527

Use of predictable filenames in Ivanti Connect Secure before versions 25.1.1.3 and 22.8R2.6 allows a remote authenticated attacker to upload files with attacker-controlled content to a known location on disk.

CVSS: 4.3Mediumscored by the publisher (CNA)
Exploited in the wild: Yes, in CISA KEV since 30 Oct 2026CISA deadline for US federal agencies: 13 Nov 2026
EPSS: 0.82%chance of exploitation in the next 30 daystop 43% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 3 Nov 2026analysed here 12 Nov 2026

Do first. 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. (CISA's required action for this KEV entry)

Summary

Triage

Exploitable: At runtime
Attack vector: network
Weakness: CWE-340 Common Weakness

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

ivanti:connect_secure

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. The attacker must be authenticated and uploads files with predictable filenames to a known location. The malicious request looks like a normal authenticated file upload, so a WAF cannot reliably distinguish it from legitimate uploads.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Listed since 30 Oct 2026.
CISA due date: 13 Nov 2026, the remediation deadline for US federal agencies
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 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.
Public exploit code: None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC: exploitation active, automatable no, technical impact partialAssessed by CISA 3 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

30 Oct 2026Added to CISA KEV (exploited in the wild)
3 Nov 2026Published5 days later
3 Nov 2026CISA SSVC assessment: exploitation activesame day later
3 Nov 2026CVE record last updatedsame day later
12 Nov 2026Analysed by vulneraibility.com9 days later
13 Nov 2026CISA remediation due date (US federal agencies)1 day later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	LowThe attacker needs basic user privileges.	The attacker needs basic user privileges.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	NoneNo data disclosure.	No data disclosure.
Integrity	LowLimited modification possible.	Limited modification possible.
Availability	NoneThe service stays up.	The service stays up.

Common questions

Is CVE-2026-118527 being exploited?

Yes. CVE-2026-118527 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-118527?

CVE-2026-118527 is rated Medium with a CVSS score of 4.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-118527?

Yes. A fix has been recorded for CVE-2026-118527. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-118527 affect?

CVE-2026-118527 affects ivanti:connect_secure. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

2 references in the CVE record, grouped by the tags the record gives them.

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.