CVE-2025-20292: Cisco NX-OS Software · OS Command Injection
Affects Cisco NX-OS SoftwareSource CVE Database V5
Not known to be exploited · CVSS 4.4 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 3.1% chance of exploitation in 30 days – higher than 87% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation 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 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Cisco Cisco NX-OS Software | Affected
| Fixed in– |
AI-suggested
European organizations should implement a multi-layered mitigation approach beyond generic advice: 1) Immediately audit and restrict CLI access to Cisco NX-OS devices, enforcing the principle of least privilege and using strong authentication mechanisms such as multi-factor authentication (MFA) for all administrative accounts. 2) Monitor and log all CLI activities to detect anomalous commands or input patterns indicative of injection attempts. 3) Apply Cisco’s security advisories and patches as soon as they become available; in the interim, consider upgrading to unaffected NX-OS versions or applying configuration workarounds recommended by Cisco. 4) Conduct regular credential reviews and rotate passwords to reduce the risk of credential compromise. 5) Segment network management interfaces to isolate NX-OS devices from general user networks, limiting local access to trusted administrators only. 6) Employ host-based intrusion detection systems (HIDS) on network devices where feasible to detect unauthorized file access or command execution. 7) Train network administrators on secure CLI usage and awareness of injection risks. These targeted measures will reduce the likelihood of exploitation and limit potential damage if an attacker gains authenticated access.
Description
A vulnerability in the CLI of Cisco NX-OS Software could allow an authenticated, local attacker to execute a command injection attack on the underlying operating system of an affected device. To exploit this vulnerability, the attacker must have valid user credentials on the affected device. This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by entering crafted input as the argument of an affected CLI command. A successful exploit could allow the attacker to read and write files on the underlying operating system with the privileges of a non-root user account. File system access is limited to the permissions that are granted to that non-root user account.