# CVE-2026-20037: Cisco UCS Manager File Write Vulnerability

> An authenticated local attacker with read-only privileges can escalate privileges to modify files and perform unauthorized actions on Cisco UCS Manager.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-qwj7-2gpw-fvvg

## What is CVE-2026-20037?

CVE-2026-20037 is a medium-severity vulnerability in Cisco Unified Computing System (Managed), published on 25 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in the NX-OS CLI privilege levels of Cisco UCS Manager Software could allow an authenticated, local attacker with read-only privileges to modify files and perform unauthorized actions on an affected system.
 
This vulnerability exists because unnecessary privileges are given to the user. An attacker could exploit this vulnerability by authenticating to a device as a read-only user and connecting to the NX-OS CLI. A successful exploit could allow the attacker to create or overwrite files in the file system or perform limited privileged actions on an affected device.   

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2026-20037 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-20037 is a medium-severity vulnerability in Cisco Unified Computing System (Managed), published on 25 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-20037 in the wild and no public exploit code.

Affected product: Cisco Unified Computing System (Managed). 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-20037/ (Markdown: https://insights.sbomify.com/CVE-2026-20037/index.md)
```

## Sources

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

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