# CVE-2025-20282: Cisco ISE API Unauthenticated Remote Code Execution Vulnerability

> Unauthenticated remote attackers can upload and execute arbitrary files as root on Cisco ISE devices due to missing file validation.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-w8p2-wjjr-hr24

## What is CVE-2025-20282?

CVE-2025-20282 is a critical vulnerability in Cisco Identity Services Engine, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in an internal API of Cisco ISE and Cisco ISE-PIC could allow an unauthenticated, remote attacker to upload arbitrary files to an affected device and then execute those files on the underlying operating system as root.

This vulnerability is due a lack of file validation checks that would prevent uploaded files from being placed in privileged directories on an affected system. An attacker could exploit this vulnerability by uploading a crafted file to the affected device. A successful exploit could allow the attacker to store malicious files on the affected system and then execute arbitrary code or obtain root privileges on the system.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-20282?

It affects 2 products.


Products: Cisco Identity Services Engine, Cisco Identity Services Engine Passive Identity Connector.

## How do I fix CVE-2025-20282?

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

## Is CVE-2025-20282 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-20282 exists.

Public exploit code:

- Proof of concept of CVE-2025-20282, the perfect 10. (github_poc): https://github.com/skadevare/CiscoISE-CVE-2025-20282-POC
- Cisco ISE < 3.4P2 - Unauthenticated Arbitrary File Upload (nuclei): http/cves/2025/CVE-2025-20282.yaml

## 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-2025-20282 and fix it if it is affected.

What it is: CVE-2025-20282 is a critical vulnerability in Cisco Identity Services Engine, published on 25 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-20282 exists.

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-2025-20282/ (Markdown: https://insights.sbomify.com/CVE-2025-20282/index.md)
```

## Sources

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

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