Cisco Enterprise NFV Infrastructure Software: Exposed Dangerous Method or Function
CVE-2026-20293 is a high-severity exposed dangerous method or function vulnerability in Cisco Enterprise NFV Infrastructure Software from Cisco, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected Cisco Enterprise NFV Infrastructure Software versions: 4.1.1; 3.9.1; 3.5.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Cisco Enterprise NFV Infrastructure Software you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on sec.cloudapps.cisco.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Cisco | Cisco Enterprise NFV Infrastructure Software | 4.1.1; 3.9.1; 3.5.2; 3.12.2; 3.6.2; 3.9.2; 3.11.3; 3.11.1; and 32 more ranges | Not stated |
| Cisco | Cisco Unified Computing System (Managed) | 4.0(1a); 4.1(1a); 4.1(1b); 4.0(4h); 4.1(1c); 4.0(4e); 4.0(4g); 4.0(2e); and 32 more ranges | Not stated |
| Cisco | Cisco Unified Computing System (Standalone) | 4.0(2g); 3.1(2i); 3.1(1d); 4.0(4i); 4.1(1c); 4.0(2c); 4.0(1e); 4.0(2h); and 32 more ranges | Not stated |
| Cisco | Cisco Unified Computing System E-Series Software (UCSE) | 4.11.1; 4.12.1; 4.12.2; 4.15.2; 4.15.3; 4.15.4 | Not stated |
| Cisco | Enterprise Nfv Infrastructure Software | 3.3.1; 3.4.1; 3.5.1; 3.5.2; 3.6.1; 3.6.2; 3.6.3; 3.7.1; and 32 more ranges | Not stated |
| Cisco | Unified Computing System | 4.0\(1a\); 4.0\(1b\); 4.0\(1c\); 4.0\(1d\); 4.0\(2a\); 4.0\(2b\); 4.0\(2d\); 4.0\(2e\); and 32 more ranges | Not stated |
| Cisco | Unified Computing System E-series Software | 4.11.1; 4.12.1; 4.12.2; 4.15.2; 4.15.3; 4.15.4 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by CNA (cisco.com).
Official description
A vulnerability in the Unified Extensible Firmware Interface (UEFI) Shell implementation of Cisco UCS Servers and UCS-based appliances could allow an authenticated attacker with valid credentials for a user account with the role of user or admin or an unauthenticated attacker with physical access to an affected device to bypass UEFI Secure Boot validation checks and execute unauthorized software. This vulnerability is due to the availability of memory write commands in the UEFI Shell while UEFI Secure Boot is enabled on a device. An attacker could exploit this vulnerability by selecting the UEFI Shell boot option at boot time and using available shell commands to modify UEFI memory variables. A successful exploit could allow the attacker to manipulate the preboot environment, overwrite UEFI Secure Boot-related memory values, and execute unauthorized software on the affected device.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Exposed Dangerous Method or Function
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
How developers prevent this class of flaw
- If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
- Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be: accessible to all users restricted to a small set of privileged users prevented from being directly accessible at all Ensure that the implemented code follows these expectations. This includes setting the appropriate access modifiers where applicable (public, private, protected, etc.) or not marking ActiveX controls safe-for-scripting.
More Exposed Dangerous Method or Function vulnerabilities (CWE-749)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Cisco Enterprise NFV Infrastructure Software
- 9.8 Critical severity
- 8.8 High severity
- 7.8 High severity
- 7.4 High severity
- 8.8 High severity
- 9.9 Critical severity
Recent Exposed Dangerous Method or Function vulnerabilities
- 7.4 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.2 High severity
- 7.5 High severity
Spotted an error? Tell us.