Cisco NX-OS Software: Buffer Access with Incorrect Length Value
CVE-2026-20010 is a high-severity buffer access with incorrect length value vulnerability in Cisco NX-OS Software from Cisco, with a CVSS 3.1 base score of 7.4 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected Cisco NX-OS Software versions: 10.3(1); 10.3(2); 10.3(3), 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.19% 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 NX-OS Software you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Cisco | Cisco NX-OS Software | 10.3(1); 10.3(2); 10.3(3); 10.4(1); 10.3(99w); 10.3(3w); 10.3(99x); 10.3(3o); and 9 more ranges | Not stated |
| Cisco | Cisco NX-OS System Software in ACI Mode | 16.0(2h); 16.0(2j); 16.0(3d); 16.0(3e); 16.0(4c); 16.0(5h); 16.0(3g); 16.0(5j); and 13 more ranges | Not stated |
| Cisco | Cisco Unified Computing System (Managed) | 4.3(4e); 4.3(6b); 4.3(4c); 4.3(4f); 4.3(6d); 4.3(5e); 4.3(4d); 4.3(4b); and 5 more ranges | 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
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H. Scored by CNA (cisco.com).
Official description
A vulnerability in the Link Layer Discovery Protocol (LLDP) feature of Cisco NX-OS Software could allow an unauthenticated, adjacent attacker to cause the LLDP process to restart, which could cause an affected device to reload unexpectedly. This vulnerability is due to improper handling of specific fields in an LLDP frame. An attacker could exploit this vulnerability by sending a crafted LLDP packet to an interface of an affected device. A successful exploit could allow the attacker to cause the device to reload, resulting in a denial of service (DoS) condition. Note: LLDP is a Layer 2 link protocol. To exploit this vulnerability, an attacker would need to be directly connected to an interface of an affected device, either physically or logically (for example, through a Layer 2 Tunnel configured to transport the LLDP protocol).
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Buffer Access with Incorrect Length Value
The product uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
More Buffer Access with Incorrect Length Value vulnerabilities (CWE-805)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in Cisco NX-OS Software
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Recent Buffer Access with Incorrect Length Value vulnerabilities
- 7.4 High severity
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 7.3 High severity
- 8.6 High severity
Spotted an error? Tell us.