The Coe Lab
← Back to Security

CVE-2026-118527: Ivanti Connect Secure predictable file upload is being chained in active attacks — CISA gives defenders until November 13

By November 5, 202611 min read
CVE AnalysisCVE-2026-118527Cybersecurity
A technology notebook with visual symbols for AI, cybersecurity, infrastructure, and automation

CISA added CVE-2026-118527 to its exploited catalog before the CVE was even public. A medium-severity file upload becomes serious when chained with other Ivanti flaws. Patch to 25.1.1.3 or 22.8R2.6 by November 13.

CoeLab Real-World Impact: 81/100 — High. Editorial score v1.0. Evidence checked 2026-11-05T10:10:25.357974+00:00. CVSS and EPSS are separate measures, not this editorial score.

Rating breakdown: exploitation: 30, reachability: 20, consequences: 11, operational relevance: 20.

Who is affected

CVE-2026-118527 affects Ivanti Connect Secure, the VPN and network-access gateway product deployed widely at the edge of enterprise and government networks. Ivanti's CVE record designates Connect Secure as affected by default, and names two fixed releases: 25.1.1.3 on the current 25.1 line and 22.8R2.6 on the maintenance line. Any deployment running a version earlier than those two releases falls within the affected range.

NVD's analyzed configuration data makes the affected window concrete: the 25.1 line from 25.1.0.0 up to, but not including, 25.1.1.3, and the 22.8 R2 release series at R2, R2.1, R2.2, R2.3, R2.4, and R2.5. Administrators running 22.7 or earlier long-term builds should not assume they are safe by omission; the vendor record expresses defaultStatus affected for the product, and Ivanti's advisory page for the companion CVE-2026-104935 is the authoritative place to confirm whether an older branch received a fix. Ivanti's advisory hub serves content through JavaScript, which limited what could be quoted directly here, so version statements below are taken from Ivanti's own published CVE record as enriched on NVD.

The practical affected population is anyone who operates Connect Secure as a remote-access gateway: employees connecting from laptops, contractors, and in many cases appliances directly exposed to the internet. That exposure profile is exactly the kind CISA's Binding Operational Directive 26-04 patching guidance treats as prioritized, and it is why deadline-driven remediation matters more here than for a typical internal server.

Real-world impact and exploitation evidence

On its face this is a modest bug. The issue is classified as CWE-340, generation of predictable numbers or identifiers: an authenticated attacker can upload files whose names are predictable, landing content they control at a known location on the appliance's disk. Ivanti's own severity metric is CVSS 3.1 base score 4.3, medium, with network attack vector, low privileges required, and an integrity-only impact. Taken in isolation, an integrity-only 4.3 does not justify panic.

The context changes the picture. CISA coordinated this vulnerability and recorded SSVC decision data marking exploitation as active, with technical impact partial and the issue not automatable. CISA added CVE-2026-118527 to the Known Exploited Vulnerabilities catalog on October 30, 2026, which is itself notable: the KEV listing predates the CVE record's publication on November 3, 2026. In other words, CISA treated exploitation evidence as strong enough to catalog the flaw before the public CVE record existed. Federal agencies' remediation deadline is November 13, 2026.

The KEV entry's stated reason is chaining: CISA notes the vulnerability can be combined with CVE-2026-104935 and CVE-2026-111357, both also Ivanti Connect Secure issues covered in the companion advisory cited in the KEV notes. A predictable-location file write with attacker-controlled content is a classic ingredient for escalation in a chain — placing files where another flaw or a service boundary will consume them — which is why the catalog treats this as exploited in active campaigns despite the low standalone score.

One editorial caution: EPSS for this CVE is currently low, about 0.8 percent as of November 4, and the KEV entry does not name specific victims or ransomware campaigns (known ransomware use is recorded as unknown). The exploitation evidence rests on CISA's cataloging decision and its SSVC active-exploitation determination, not on public proof-of-concept details. Defenders should treat it as a real but not yet mass-exploited issue, with the caveat that KEV listing frequently precedes broader weaponization.

CoeLab's Real-World Impact v1.0 score for this CVE is 81, rated High, built from four components. Exploitation earned the full 30 points because of the KEV listing (the model's strongest signal, though it measures cataloging evidence, not attack volume). Reachability earned 20 of 25 from the published CVSS vector: network vector and low privileges required, with low complexity absent. Consequences contributed only 11 of 25, because the component multiplies the published base score (4.3) by 2.5 — this is where the model honestly shows the flaw's standalone severity is modest. Operational relevance earned the full 20 points as a documented edge-device product. The limitations are important: the score is neither CVSS nor EPSS, it inherits CVSS's weaknesses where the base score understates chained risk, and the KEV component cannot distinguish targeted exploitation from widespread campaigns. A reader should see 81 as a prioritization heuristic that leans heavily on the fact of active exploitation. Scores at 70 or above pass the editorial floor, but they are necessary, not sufficient; the editorial judgment here rests on the deadline and the chaining context rather than the number alone.

Attack prerequisites

Exploitation requires prior authentication to the appliance — the CVSS vector specifies privileges required low, not none. An attacker therefore needs some foothold as a legitimate or lightly privileged user: a stolen VPN credential, a session obtained through credential phishing, or a companion flaw that grants initial access. CISA's SSVC assessment marks the vulnerability as not automatable, consistent with the need for authenticated access and with the lack of a documented unauthenticated path.

This prerequisite cuts both ways for defenders. It means an unauthenticated internet attacker cannot simply fire an exploit at the appliance cold, which is why mass scanning is not the primary threat model. It also means environments that have already suffered credential theft or a chained initial foothold — the standard Ivanti incident pattern in recent years — should assume this flaw is usable against them. Authentication is a barrier to opportunistic attacks, not a boundary against a determined actor who already holds one stolen credential.

The chaining statement in the KEV entry defines the realistic scenario: this CVE functions as a stage in a sequence alongside CVE-2026-104935 and CVE-2026-111357 rather than as a one-shot take-over bug. Organizations should read those companion CVE records and the same Ivanti advisory together when triaging.

Actions and fixes

Upgrade Ivanti Connect Secure to 25.1.1.3 on the 25.1 line or 22.8R2.6 on the 22.8 line; those are the two releases Ivanti's published record lists as unaffected by this vulnerability. Both fixes were in place before the CVE record went public on November 3, so patches predate the record's publication and the fix delivery is not the bottleneck — deployment speed is.

Treat the federal deadline of November 13, 2026 under CISA's BOD 26-04 guidance as a reasonable target even for private organizations, prioritizing appliances that face the internet or terminate connections for many users. Because exploitation is already cataloged as active, patching should be paired with posture work Ivanti and CISA typically recommend for Connect Secure: review appliance integrity, rotate credentials used for administrative and VPN access where compromise is suspected, and check logs for unexplained uploads or sessions around known exploit windows. CISA's required action also points organizations to its forensic triage requirements, a signal that simple patching without a compromise check may be insufficient for an actively exploited edge device.

Finally, inventory matters. Appliance products like Connect Secure are frequently forgotten between major upgrades, and long-running 22.8 R2 subversions sit in many estates. A quick version audit this week is the cheapest risk reduction available; administrators on branches older than 22.8 R2 should consult Ivanti's advisory for their upgrade path rather than assume coverage.

Uncertainty and what could change

Several facts remain open. The vendor advisory page itself could not be retrieved as plain text when this was written; its content is only represented here through Ivanti's published CVE record and CISA's enrichment, so if Ivanti revises affected branches or adds fix releases, those changes will supersede the versions named above. The record has been updated once already (November 3), and CISA's catalog entry could gain new notes, ransomware attribution, or a revised requirement.

Exploitation breadth is uncertain in both directions. EPSS is low today, and no public campaign attribution exists, so it is possible exploitation so far is limited and targeted. It is equally possible that the chaining recipe becomes broadly abused now that the CVE record makes the mechanics explicit. Watch for KEV catalog updates, EPSS movement, and any Ivanti advisory revision over the next two weeks; a rise in EPSS or new companion CVE activity would justify escalating urgency beyond the deadline framing used here.

The standalone CVSS score of 4.3 will likely cause some organizations to deprioritize this patch, and that is the main scenario in which the real risk diverges from the published score. If you manage Connect Secure, plan around the chain and the deadline rather than around the number.

Sources and evidence date

This analysis draws on three primary sources consulted November 5, 2026: the CVE record for CVE-2026-118527 assigned and published by Ivanti (record published 2026-11-03, last updated 2026-11-03), the NVD analyzed record enriching that data with CVSS scores, configuration ranges, CISA SSVC decisions, and KEV metadata, and the CISA Known Exploited Vulnerabilities catalog entry dated 2026-10-30 with the November 13 federal remediation deadline. Ivanti's own advisory page for the companion CVE-2026-104935, referenced by both the CVE record and the KEV notes, is linked in the source list for readers who want the vendor's full text.

Timeline of dates, kept distinct: vulnerability discovery and internal coordination date is not separately published; the CVE was reserved October 28, 2026; CISA added it to KEV October 30, 2026; the CVE record was published November 3, 2026; EPSS was sampled November 4, 2026; this review's evidence snapshot was taken November 5, 2026. This is a previously cataloged vulnerability now appearing for review in the news cycle because of the KEV listing and CVE publication — it is not a newly discovered flaw in the software, and it should not be described as one.

Primary-source links

https://hub.ivanti.com/s/article/Security-Advisory-Ivanti-Connect-Secure-CVE-2026-104935?language=en_US

https://www.cve.org/CVERecord?id=CVE-2026-118527

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-118527

AI-assisted research and drafting, with a separate model editorial review. CoeLab ratings are editorial judgments, not a substitute for checking your own versions and vendor advisories. Methodology: https://thecoelab.com/blog/security/methodology

Related Posts

CVE-2026-125350: Chrome XML use-after-free, now actively exploited and on CISA's KEV with a November 24 deadline

A use-after-free in Chrome's XML handling is under active exploitation per CISA. Update every Chromium-based browser to Chrome 157.0.8103.50 or later before the November 24 federal deadline.

Nov 12, 2026• 12 min

AWS Emulator: Local Tests Need a Cloud Reality Check

AWS has a local API emulator. Here is how to use faster feedback without confusing passing integration tests with proof that production will work.

Nov 12, 2026• 10 min read

CVE-2026-111560: Barracuda appliance timezone command injection — now on CISA's KEV with a November 13 patch deadline

Authenticated admin command injection to root across six Barracuda appliances, chainable with a pre-auth bypass; KEV-listed with actions due November 13.

Nov 11, 2026• 11 min