CVE-2025-20295VulnerabilityPublished 27 Aug 2025Updated 26 Feb 2026

CVE-2025-20295: Cisco Unified Computing System (Managed) · OS Command Injection

Affects Cisco Unified Computing System (Managed)Source CVE Database V5

Not known to be exploited · CVSS 6.0 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

6.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-20295, organizations should: 1) Immediately apply any patches or updates released by Cisco addressing this vulnerability once available. 2) Restrict administrative access to Cisco UCS Manager to a minimal set of trusted personnel and enforce strong authentication mechanisms, such as multi-factor authentication. 3) Monitor administrative account usage and audit CLI commands for suspicious activity that could indicate exploitation attempts. 4) Implement network segmentation to limit access to UCS Manager interfaces, reducing exposure to potential attackers. 5) Regularly review and rotate administrative credentials to reduce the risk of credential compromise. 6) Employ host-based intrusion detection systems on UCS Manager hosts to detect unauthorized file modifications. 7) Consider deploying compensating controls such as command whitelisting or input validation proxies if patching is delayed. 8) Conduct security awareness training for administrators to recognize and report anomalous system behavior. These steps go beyond generic advice by focusing on access control, monitoring, and layered defense tailored to the UCS environment.

Description

A vulnerability in the CLI of Cisco UCS Manager Software could allow an authenticated, local attacker with administrative privileges to read or create a file or overwrite any file on the file system of the underlying operating system of an affected device, including system files.   This vulnerability is due to insufficient input validation of command arguments supplied by the user. An attacker could exploit this vulnerability by authenticating to a device and submitting crafted input to the affected command. A successful exploit could allow the attacker to read or create a file or overwrite any file on the file system of the underlying operating system of the affected device, including system files. To exploit this vulnerability, the attacker must have valid administrative credentials on the affected device.

Impact

The potential impact of CVE-2025-20295 is substantial for organizations using Cisco UCS Manager to control their server infrastructure. An attacker exploiting this vulnerability can manipulate system files, potentially leading to unauthorized disclosure of sensitive data, modification or deletion of critical configuration files, and disruption of normal operations. This could facilitate further attacks such as privilege escalation, persistence mechanisms, or lateral movement within a network. Since the vulnerability requires administrative credentials, the risk is primarily from insider threats or attackers who have already compromised administrative accounts. However, the ability to overwrite system files elevates the threat to system integrity and availability indirectly. Organizations relying heavily on Cisco UCS for data center management could face operational downtime, data breaches, or compliance violations if this vulnerability is exploited. The widespread affected versions indicate many deployments are at risk, emphasizing the need for timely remediation.

References

sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-ucs-multi-cmdinj-E4Ukjyrz (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 27 Feb 2026, 00:22 UTC

Technical details

References

Community reviews

Related threats