Skip to main content
VulnerabilityPublished

CVE-2026-20048: Cisco NX-OS System Software in ACI Mode · Uncontrolled Memory Allocation

Affects Cisco NX-OS System Software in ACI ModeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
CiscoCisco NX-OS System Software in ACI ModeAffected
  • 15.2(1g) – 16.1(4h)
57 affected builds
Fixed in–

AI-suggested

  1. Apply Cisco's security patches or software updates for NX-OS versions addressing this vulnerability as soon as they become available.
  2. Restrict SNMP access strictly to trusted management stations and networks using access control lists (ACLs) and firewall rules to minimize exposure.
  3. Enforce strong SNMP authentication by using SNMPv3 with robust user credentials and disable SNMPv1 and SNMPv2c where possible.
  4. Regularly audit SNMP community strings and user accounts to ensure they are complex, unique, and rotated periodically.
  5. Monitor SNMP traffic for unusual patterns such as repeated queries to specific MIBs that could indicate exploitation attempts.
  6. Implement network segmentation to isolate management interfaces from general user networks.
  7. Employ intrusion detection/prevention systems (IDS/IPS) capable of detecting anomalous SNMP activity.
  8. Conduct regular vulnerability assessments and penetration testing focused on network management protocols.
  9. Educate network administrators on secure SNMP configuration and the risks of credential exposure.
  10. Maintain up-to-date inventory of affected devices and versions to prioritize remediation efforts effectively.

Description

A vulnerability in the Simple Network Management Protocol (SNMP) subsystem of Cisco Nexus 9000 Series Fabric Switches in ACI mode could allow an authenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to improper processing when parsing SNMP requests. An attacker could exploit this vulnerability by continuously sending SNMP queries to a specific MIB of an affected device. A successful exploit could allow the attacker to cause a kernel panic on the device, resulting in a reload and a DoS condition. Note: This vulnerability affects SNMP versions 1, 2c, and 3. To exploit this vulnerability through SNMPv1 or SNMPv2c, the attacker must have a valid read-only SNMP community string for the affected system. To exploit this vulnerability through SNMPv3, the attacker must have valid SNMP user credentials for the affected system.

References

Community reviews

Loading reviews…