# CVE-2026-104935: Ivanti Connect Secure Authentication Bypass by Spoofing

> Remote unauthenticated attackers can bypass authentication via spoofing to execute arbitrary commands on Ivanti Connect Secure ICS.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Yes, since 13 Oct 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-vm2g-whwh-xhq8

## What is CVE-2026-104935?

CVE-2026-104935 is a high-severity authentication bypass vulnerability in Ivanti Connect Secure, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication bypass by spoofing in ICS before version 25.1.3.0 allows a remote unauthenticated attacker to execute arbitrary commands. This does not impact ICS version 22.7R2.14 or prior.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2026-104935?

It affects 1 product.


Products: Ivanti Connect Secure.

## How do I fix CVE-2026-104935?

No fix has been published for CVE-2026-104935 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 16 Oct 2026.

## Is CVE-2026-104935 being exploited?

Yes. Attackers have exploited CVE-2026-104935 in the wild since at least 13 Oct 2026.

Public exploit code:

- Unauthenticated remote code execution in Ivanti Connect Secure (CWE-290, CVSS 8.6) (github_poc): https://github.com/ApexBreach/CVE-2026-104935-Proof-of-concept
- Detection-only check for the Ivanti Connect Secure authentication bypass (CVE-2026-104935) (github_poc): https://github.com/0x45dd/ivanti-cve-2026-104935-check
- CVE-2026-104935 — Ivanti Connect Secure / Pulse Secure RCE Exploit (github_poc): https://github.com/maxprog-svg/CVE-2026-104935
- Bluefire Redteam checker for Ivanti Connect Secure CVE-2026-104935. Version and reachability only. (github_poc): https://github.com/Bluefire-Redteam-Cybersecurity/bluefire-ivanti-ics-guard
- Offline Ivanti Connect Secure evidence checker for CVE-2026-104935. Connect Secure build and configuration evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads. (github_poc): https://github.com/CompleteTech-Security/ivanti-connect-secure-cve-2026-104935-check
- Ivanti Connect Secure <= 22.8R2.4 - Authentication Bypass via X-DSCGI-PATH Header (nuclei): http/cves/2026/CVE-2026-104935.yaml

## Other vulnerabilities in Ivanti Connect Secure

- [CVE-2021-22893](https://insights.sbomify.com/CVE-2021-22893/): Ivanti Pulse Connect Secure Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2019-11510](https://insights.sbomify.com/CVE-2019-11510/): Ivanti Pulse Connect Secure Arbitrary File Read (critical 9.9, exploited in the wild)
- [CVE-2024-21887](https://insights.sbomify.com/CVE-2024-21887/): Ivanti Connect Secure and Policy Secure Command Injection (critical 9.1, exploited in the wild)
- [CVE-2025-22457](https://insights.sbomify.com/CVE-2025-22457/): Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow (critical 9.0, exploited in the wild)
- [CVE-2025-0282](https://insights.sbomify.com/CVE-2025-0282/): Ivanti Connect Secure, Policy Secure, and ZTA Gateways Stack-Based Buffer Overflow (critical 9.0, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104935 and fix it if it is affected.

What it is: CVE-2026-104935 is a high-severity authentication bypass vulnerability in Ivanti Connect Secure, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-104935 in the wild since at least 13 Oct 2026.

Affected product: Ivanti Connect Secure. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104935/ (Markdown: https://insights.sbomify.com/CVE-2026-104935/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104935
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104935
- OSV: https://osv.dev/vulnerability/CVE-2026-104935

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104935/
Summaries are generated and may contain mistakes; the official description above is the record.