External risk intelligence

Cisco NX-OS VXLAN OAM Code Execution and DoS Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-76485

The vulnerability affects the VXLAN OAM feature in Cisco NX-OS, which is intended for network infrastructure management and internal traffic control. While reachable via network packets, these devices are typically deployed within core network fabrics or internal data center segments, making direct exposure to the public internet highly uncommon in standard deployment patterns.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability involves a flaw in Cisco's network operating system that could allow an attacker to take control of devices or disrupt their operations. The issue stems from how the system handles certain network traffic, potentially enabling an attacker to execute malicious code or cause service interruptions.

  • Flaw allows remote takeover or disruption.
  • Crucial for network infrastructure integrity.
  • Verify exposure within our network.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker could exploit this vulnerability by sending specially crafted IP packets to a device running a vulnerable version of Cisco NX-OS Software. This attack targets the VXLAN OAM feature, which is enabled by default on some platforms. Successful exploitation could allow the attacker to execute arbitrary code with full administrative privileges or cause a denial-of-service condition.

  • No authentication or user interaction needed.
  • Crafted IP packets sent to a vulnerable device.
  • Arbitrary code execution or denial-of-service.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could impact network devices running Cisco NX-OS Software with the VXLAN OAM feature enabled. An unauthenticated, remote attacker could exploit this by sending crafted IP packets to an affected device, potentially leading to arbitrary code execution with root privileges or a denial-of-service condition that causes process crashes and device reloads.

  • Network device integrity and availability.
  • Sending crafted IP packets to the device.
  • Device compromise or denial-of-service.

Operational Fix

Recommended remediation, mitigation, and detection steps

Network infrastructure teams managing Cisco network devices are most likely responsible for addressing this vulnerability. The initial step should be to identify all devices running Cisco NX-OS with the VXLAN OAM feature enabled, confirm their network exposure, and then determine the accountable system owner to plan remediation.

  • Network infrastructure teams own this vulnerability.
  • Verify VXLAN OAM feature usage and network exposure.
  • Plan remediation considering business criticality and maintenance windows.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Cisco NX-OS Software and the NGOAM feature?

Cisco NX-OS is a data center-grade network operating system used to manage complex switching fabrics and routing. The NGOAM (VXLAN Operation, Administration, and Maintenance) feature is a built-in diagnostic toolset that helps network engineers monitor and verify the connectivity and health of VXLAN tunnels, which are used to extend Layer 2 networks over Layer 3 infrastructures.

What does CWE-121 mean for CVE-2026-76485?

CWE-121 refers to a stack-based buffer overflow. In the context of this vulnerability, it means the software fails to properly check the size of incoming data packets before copying them into memory. Because this specific flaw occurs in the NGOAM feature, sending a malformed packet allows an attacker to overwrite memory, potentially leading to unauthorized command execution.

How is this vulnerability triggered?

An attacker triggers this by sending specially crafted IP packets directly to an interface on a device where the NGOAM feature is active. Importantly, the vulnerability does not trigger if NGOAM is disabled; furthermore, since the flaw is specific to this diagnostic feature, traffic that does not conform to the expected NGOAM protocol structure will not activate the code path leading to the buffer overflow.

Is my network device at risk of this vulnerability?

According to Halo Surface Signal, risk is generally lower if your devices are strictly contained within core network or data center segments. While the vulnerability is technically reachable via network packets, it is not common for these specific management interfaces to be directly exposed to the public internet in standard, well-architected network deployments.

What are the first steps to address this CVE?

Start by auditing your network inventory to identify which devices are running Cisco NX-OS and specifically determine if the NGOAM feature is enabled. Once you have a list of active NGOAM instances, prioritize them based on their placement in your network architecture, starting with those that have higher potential connectivity, to plan your next maintenance steps.

References