Vigilbase CVEConnect your agent

Ivanti Connect Secure Missing Authentication for Critical Function Vulnerability

Exploited · KEV 2026-10-30Trending #12CVE-2026-111357CWE-829

Exploited since 2026-10-30. No WAF vendor names it yet.

Edge rules
0/8
Our test
No exploit yet
CVSS
7.0
EPSS
0.5% Top 55%
Posts, 14d
42026-10-20: 0 posts2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 4 posts
Published
2026-10-15

Ivanti Connect Secure 22.8R2.4 mishandles the manner in which the dsinvoked broker trusts DSCache configuration data, leading to privilege escalation to root, as exploited in the wild in October 2026.

Ask Vigil

AI · answers from this page
Ask about CVE-2026-111357: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Severity, decoded

CVSS 3.1
High · 7.0 / 10

Exploitable with local access under specific conditions, with low privileges and no user interaction, leading to full loss of confidentiality, integrity and availability.

Needs local accessAny user loginNo user actionHard to pull offFull compromise
How the score is built8 metrics
  • Attack vectorAn attacker needs local access, or must trick a user into opening something on the machine.
    Local
  • Attack complexityThe attack only works when conditions outside the attacker's control line up.
    High
  • Privileges requiredThe attacker needs an ordinary user account.
    Low
  • User interactionNo one has to click or open anything; the attack works on its own.
    None
  • ScopeThe damage stays within the vulnerable component.
    Unchanged
  • Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.
    High
  • Integrity impactAn attacker can change any data or files the affected component protects.
    High
  • Availability impactAn attacker can take the component down completely or keep it from serving anyone.
    High
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA's assessmentSSVC, from the CVE record
ExploitationActive

Attackers are exploiting this in the wild.

AutomatableNo

At least one step needs hands-on work, which slows mass attacks.

Technical impactTotal

A successful attack gives full control over the affected software or all of its data.

Public exploits

None found
0 Metasploit0 Exploit-DB0 Scanner template0 GitHub PoCs

No exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.

Timeline

  1. 2026-10-15
    CVE published
    CVE List
  2. 2026-10-30
    Added to CISA KEV
    Confirmed exploitation in the wild
  3. 2026-11-02
    First social mention we saw

Social

2026-10-20: 0 posts2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 4 posts

Top posts

  • DFIR Radar@DFIR_Radar·

    Three chained Ivanti Connect Secure zero-days (CVE-2026-104935, CVE-2026-111357, CVE-2026-118527) exploited in the wild since October 3, granting unauthenticated root access. All three are now in CISA KEV. Patches exist for all three as of October 29. Key findings: - The chain…

    ♥ 1View on X
  • ADK Cyber@ADKCyber·

    Ivanti patched two new zero-days in Connect Secure (CVE-2026-111357, CVE-2026-118527) chained in attacks and added to CISA KEV. Review and update VPN instances. https://t.co/YGPNdY0Uv7 via SecurityWeek #CyberSecurity #InfoSec #Vulnerability #AI #MachineLearning https://t.co/S4…

    View on X
  • alt@alt.pds.lefht.cc·

    4. CVE-2026-111357 · 9 people 🔥 🟧 High 7.0 · Ivanti Connect Secure Ivanti Connect Secure 22.8R2.4 mishandles the manner in which the dsinvoked broker trusts DSCache configuration data, leading to privilege escalation to root, as exploited in the wild in October 2026.

    View on Bluesky
  • alt@alt.pds.lefht.cc·

    🛡️ Most-discussed CVEs on Bluesky, last 24h 1. CVE-2026-98432 · 33 people 2. CVE-2026-97229 · 10 people 🔥 3. CVE-2026-109618 · 9 people 🔥 4. CVE-2026-111357 · 9 people 🔥 5. CVE-2026-118527 · 8 people 🔥 🔥 = on CISA's Known Exploited list · details in the thread 🧵

    View on Bluesky

Vendor statements

Quoted
CloudflareWAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each row gives the rule ID and its default action. The feed starts in January 2025, so older rules are missing.

AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.

Google CloudCloud Armor preconfigured WAF rulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.

FastlyNext-Gen WAF virtual patchesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The feed holds only the latest 25 changes, so history builds up from the day we started reading it.

F5Attack signatures (Distributed Cloud WAF)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Each signature lists the CVEs it references, with its id and date. F5 does not state a default action; signatures enforce once staging ends in your policy.

AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.