CVE-2026-76471

Vulnérabilité critique dans Cisco NX-OS Software (Cisco)

CVSS 9.8 · Critique
EPSS 0.5%
Cisco•Cisco NX-OS Software•Versions : 4.1(3c), 9.3(1), 4.2(1c), 4.2(2e), 9.3(8), 4.3(5d), 4.1(3h), 4.2(1i), 10.5(1), 10.5(4), 4.2(2c), 4.1(3n), 4.0(4o), 10.6(1), 9.2(4), 10.3(3q), 4.2(3h), 9.3(10), 4.3(4b), 10.3(99x), 10.3(4a), 10.3(7), 4.2(3d), 4.3(6e), 10.5(3t), 4.2(1k), 4.0(4k), 4.3(5c), 10.4(7), 9.3(5), 10.4(4g), 4.1(1b), 4.1(3a), 9.2(2t), 10.3(5), 4.0(2b), 4.3(5e), 9.3(4), 10.5(2), 10.3(3r), 4.2(3o), 9.2(1), 4.2(3r), 4.0(4m), 4.3(6b), 4.0(1d), 10.4(3), 9.3(5w), 9.3(14), 10.5(3p), 4.3(6h), 4.3(3a), 9.3(2), 4.0(1a), 4.1(2b), 10.6(3), 4.1(3j), 4.1(1d), 4.3(4a), 4.2(3j), 4.2(3l), 9.3(6), 4.2(3i), 4.0(4h), 4.1(1e), 4.1(3l), 4.1(4a), 4.2(3p), 4.2(3e), 4.2(3s), 10.6(3s), 4.3(4d), 4.1(1a), 9.3(17), 4.0(4d), 4.2(1f), 9.3(7a), 4.2(3b), 4.1(3m), 4.0(4i), 9.3(11), 10.3(4), 10.3(4g), 10.5(3), 10.3(2), 4.3(5a), 4.3(2c), 10.3(1), 4.0(2d), 4.2(3n), 4.1(3e), 9.2(2v), 9.3(1z), 10.6(1s), 4.3(2f), 4.0(4c), 4.3(4e), 10.3(8), 10.4(6), 9.3(15), 9.2(3y), 4.0(4n), 10.6(2n), 10.6(2), 10.3(3w), 10.4(5), 10.3(3o), 4.3(6f), 4.0(4l), 9.3(7), 10.3(3p), 4.2(2d), 4.2(1n), 10.5(3o), 4.3(6i), 10.3(3x), 4.1(2c), 4.2(1m), 4.0(4f), 4.1(3b), 9.3(13), 4.0(1b), 4.1(1c), 9.2(3), 10.6(2s), 4.3(6g), 4.0(4a), 10.3(4h), 4.2(3g), 4.1(2a), 4.1(3k), 9.2(2), 10.4(1), 4.2(2a), 10.4(4), 4.3(3c), 4.2(3m), 10.3(99w), 4.1(3f), 10.3(9), 9.3(7k), 4.3(2e), 10.5(3s), 4.2(1d), 4.3(6d), 10.4(2), 4.0(4e), 9.3(16), 9.3(3), 4.0(4g), 10.5(3e), 4.0(1c), 10.5(5), 9.3(12), 4.2(1l), 10.3(6), 4.3(2b), 4.3(6c), 4.1(3d), 4.3(4f), 10.3(3), 4.1(3i), 4.0(2a), 9.3(9), 4.0(4b), 4.3(6a), 4.0(2e), 4.3(4c), 4.2(3k)

Description

A vulnerability in the NX-API feature of Cisco NX-OS Software could allow an unauthenticated, remote attacker to execute arbitrary code with root privileges or cause a denial of service (DoS) condition on an affected device.  The vulnerability is due to insufficient input validation of data that is sent to the NX-API. An attacker could exploit this vulnerability by sending a crafted HTTP request to the NX-API of an affected device. A successful exploit could allow the attacker to execute arbitrary code with root privileges and could cause process crashes, which could result in a reload of the device and a DoS condition.

Gravité et risque d'exploitation

CVE-2026-76471 obtient un score CVSS de 9.8/10, soit une gravité critique. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.52 %, ce qui la place devant 43.2 % des CVE référencées.

Que faire ?

  • Vérifiez si Cisco NX-OS Software (versions 4.1(3c), 9.3(1), 4.2(1c), 4.2(2e), 9.3(8), 4.3(5d), 4.1(3h), 4.2(1i), 10.5(1), 10.5(4), 4.2(2c), 4.1(3n), 4.0(4o), 10.6(1), 9.2(4), 10.3(3q), 4.2(3h), 9.3(10), 4.3(4b), 10.3(99x), 10.3(4a), 10.3(7), 4.2(3d), 4.3(6e), 10.5(3t), 4.2(1k), 4.0(4k), 4.3(5c), 10.4(7), 9.3(5), 10.4(4g), 4.1(1b), 4.1(3a), 9.2(2t), 10.3(5), 4.0(2b), 4.3(5e), 9.3(4), 10.5(2), 10.3(3r), 4.2(3o), 9.2(1), 4.2(3r), 4.0(4m), 4.3(6b), 4.0(1d), 10.4(3), 9.3(5w), 9.3(14), 10.5(3p), 4.3(6h), 4.3(3a), 9.3(2), 4.0(1a), 4.1(2b), 10.6(3), 4.1(3j), 4.1(1d), 4.3(4a), 4.2(3j), 4.2(3l), 9.3(6), 4.2(3i), 4.0(4h), 4.1(1e), 4.1(3l), 4.1(4a), 4.2(3p), 4.2(3e), 4.2(3s), 10.6(3s), 4.3(4d), 4.1(1a), 9.3(17), 4.0(4d), 4.2(1f), 9.3(7a), 4.2(3b), 4.1(3m), 4.0(4i), 9.3(11), 10.3(4), 10.3(4g), 10.5(3), 10.3(2), 4.3(5a), 4.3(2c), 10.3(1), 4.0(2d), 4.2(3n), 4.1(3e), 9.2(2v), 9.3(1z), 10.6(1s), 4.3(2f), 4.0(4c), 4.3(4e), 10.3(8), 10.4(6), 9.3(15), 9.2(3y), 4.0(4n), 10.6(2n), 10.6(2), 10.3(3w), 10.4(5), 10.3(3o), 4.3(6f), 4.0(4l), 9.3(7), 10.3(3p), 4.2(2d), 4.2(1n), 10.5(3o), 4.3(6i), 10.3(3x), 4.1(2c), 4.2(1m), 4.0(4f), 4.1(3b), 9.3(13), 4.0(1b), 4.1(1c), 9.2(3), 10.6(2s), 4.3(6g), 4.0(4a), 10.3(4h), 4.2(3g), 4.1(2a), 4.1(3k), 9.2(2), 10.4(1), 4.2(2a), 10.4(4), 4.3(3c), 4.2(3m), 10.3(99w), 4.1(3f), 10.3(9), 9.3(7k), 4.3(2e), 10.5(3s), 4.2(1d), 4.3(6d), 10.4(2), 4.0(4e), 9.3(16), 9.3(3), 4.0(4g), 10.5(3e), 4.0(1c), 10.5(5), 9.3(12), 4.2(1l), 10.3(6), 4.3(2b), 4.3(6c), 4.1(3d), 4.3(4f), 10.3(3), 4.1(3i), 4.0(2a), 9.3(9), 4.0(4b), 4.3(6a), 4.0(2e), 4.3(4c), 4.2(3k)) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références