# CVE-2026-20180: Cisco Identity Services Engine Multiple Remote Code Execution Vulnerability

> Authenticated attackers can execute arbitrary commands and escalate privileges to root on Cisco ISE via crafted HTTP requests.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-6fqc-22r3-wrxm

## What is CVE-2026-20180?

CVE-2026-20180 is a critical command injection vulnerability in Cisco Identity Services Engine, published on 15 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to execute arbitrary commands on the underlying operating system of an affected device. To exploit this vulnerability, the attacker must have at least Read Only Admin credentials.

This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to obtain user-level access to the underlying operating system and then elevate privileges to root. In single-node ISE deployments, successful exploitation of these vulnerabilities could cause the affected ISE node to become unavailable, resulting in a denial of service (DoS) condition. In that condition, endpoints that have not already authenticated would be unable to access the network until the node is restored.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Cisco Identity Services Engine.

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

No fix has been published for CVE-2026-20180 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-20180 being exploited?

There is no known exploitation of CVE-2026-20180 in the wild and no public exploit code.

Public exploit code:

- https://github.com/kaleth4/CVE-2026-20180 (github_poc): https://github.com/kaleth4/CVE-2026-20180

## Other vulnerabilities in Cisco Identity Services Engine

- [CVE-2026-76460](https://insights.sbomify.com/CVE-2026-76460/): Cisco Identity Services Engine Incorrect Use of Privileged APIs (critical 10.0, exploited in the wild)
- [CVE-2025-20337](https://insights.sbomify.com/CVE-2025-20337/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2025-20281](https://insights.sbomify.com/CVE-2025-20281/): Cisco Identity Services Engine Injection (critical 10.0, exploited in the wild)
- [CVE-2026-20130](https://insights.sbomify.com/CVE-2026-20130/): Cisco Identity Services Engine Hardening Release - Improper Neutralization Vulnerabilities (critical 10.0)
- [CVE-2026-20192](https://insights.sbomify.com/CVE-2026-20192/): Cisco Identity Services Engine Hardening Release - Access Control Vulnerabilities (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-20180 is a critical command injection vulnerability in Cisco Identity Services Engine, published on 15 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-20180 in the wild and no public exploit code.

Affected product: Cisco Identity Services Engine. 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-20180/ (Markdown: https://insights.sbomify.com/CVE-2026-20180/index.md)
```

## Sources

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

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