Medium Privilege escalation

CVE-2026-20037 — Cisco UCS Manager File Write Vulnerability

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.   

Published Feb 25, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: cisco

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 0.1% (30-day exploitation probability)+0
Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

0.1%

ahead of 1% of scored CVEs · Oct 14, 2026

Affects

Cisco

Cisco Unified Computing System (Managed)

CVSS base

4.4

Medium · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Cisco Cisco Unified Computing System (Managed)).
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes matching the vulnerability class (privilege escalation), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Cisco	Cisco Unified Computing System (Managed)	version 4.2(3g)version 4.3(4a)version 4.3(3c)version 4.2(3j)version 4.3(3a)version 4.3(2e)version 4.1(3m)version 4.3(2c) and 82 more version 4.2(3i)version 4.2(3h)version 4.3(2b)version 4.1(3l)version 4.2(3k)version 4.2(3e)version 4.2(3d)version 4.2(2e)version 4.0(4o)version 4.1(3k)version 4.2(3b)version 4.2(2d)version 4.2(2c)version 4.1(3j)version 4.2(1n)version 4.2(3n)version 4.3(6e)version 4.3(6d)version 4.2(3p)version 4.3(6c)version 4.3(5e)version 4.3(6b)version 4.3(6a)version 4.3(5d)version 4.2(3o)version 4.3(5c)version 4.2(2a)version 4.3(4f)version 4.1(3n)version 4.3(4e)version 4.3(5a)version 4.2(3m)version 4.3(2f)version 4.3(4d)version 4.2(3l)version 4.3(4c)version 4.3(4b)version 4.0(4d)version 4.0(1c)version 4.1(1b)version 4.0(2d)version 4.1(1d)version 4.0(4i)version 4.0(4e)version 4.0(4f)version 4.1(1e)version 4.0(1d)version 4.0(4g)version 4.0(4h)version 4.1(2b)version 4.1(1a)version 4.0(2e)version 4.0(4b)version 4.0(4a)version 4.1(1c)version 4.0(1b)version 4.0(2a)version 4.0(1a)version 4.1(2a)version 4.0(2b)version 4.0(4m)version 4.1(3i)version 4.2(1m)version 4.0(4n)version 4.2(1l)version 4.2(1k)version 4.1(3h)version 4.2(1i)version 4.1(3f)version 4.2(1f)version 4.1(3e)version 4.0(4c)version 4.2(1d)version 4.2(1c)version 4.1(3d)version 4.1(3c)version 4.1(4a)version 4.0(4l)version 4.1(2c)version 4.1(3b)version 4.1(3a)version 4.0(4k)	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Local

Attack complexity

Low

Privileges required

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
4.4	CVSS 3.1	Medium	1.8	2.5	psirt@cisco.com via NIST National Vulnerability Database
4.4	CVSS 3.1	Medium	—	—	cisco via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N (score shown at the top: psirt@cisco.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-250 · Execution with Unnecessary Privileges

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.10%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.

endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · cisco/cisco unified computing system (managed)
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 4.4
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Deferred
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Feb 25, 2026 · cisco

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ucsm-afwae-mOg
NIST National Vulnerability Database

Elsewhere on this site

Cisco
every CVE for this vendor

Privilege escalation
same class

CWE-250
other pages naming this weakness

Related CVEs (same products)

Critical CVE-2026-76471 Cisco NX-OS Software NX-API Remote Code Execution Vulnerability 8d
High CVE-2026-76457 Cisco NX-OS Software Security Hardening Release: October 2026 - Out-of-bounds Read Vulnerabilities 8d
High CVE-2026-76458 Cisco NX-OS Software Security Hardening Release: October 2026 - Improper Handling of Exceptional Conditions Vulnerabilities 8d
Critical CVE-2026-76459 Cisco NX-OS Software Security Hardening Release: October 2026 - Out-of-bounds Write Vulnerabilities 8d
Critical CVE-2026-76455 Cisco NX-OS Software Security Hardening Release: October 2026 - Improper Access Control Vulnerabilities 8d
High CVE-2026-76453 Cisco NX-OS Software Security Hardening Release: October 2026 - Improper Neutralization Vulnerabilities 8d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-20037 is "Cisco UCS Manager File Write Vulnerability", rated Medium. It affects Cisco Unified Computing System (Managed) (Cisco); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.4 describes technical severity. EPSS 0.10% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.