Critical [CVE-2026-76453 +5] Cisco NX-OS Software Security Hardening Release: October 2026
This critical-severity Cisco advisory covers CVE-2026-76453 and CVE-2026-76455 and 4 more CVEs affecting NX-OS System Software in ACI Mode, Unified Computing System (Managed), NX-OS Software.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations. This bulletin covers 6 CVEs; its score, affected versions and guidance may apply to different issues within that bulletin.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Cisco CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco NX-OS Software engineering team has conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities.
These vulnerabilities were found during internal testing and are not known to be actively exploited. To assist customers in patching and streamline the disclosure process, Cisco has grouped these issues by their underlying vulnerability class — Common Weakness Enumeration (CWE) — and assigned a single Common Vulnerabilities and Exposures identifier (CVE ID).
Cisco has released software updates that address these vulnerabilities. There are no workarounds that address these vulnerabilities.
Affected products named by the advisory: NX-OS System Software in ACI Mode; Unified Computing System (Managed).
- Scope: These vulnerabilities affect the following Cisco products if they are running a vulnerable release of Cisco NX-OS Software, regardless of device configuration:
- 9.3 and earlier — Migrate to a fixed release
- Release 9.4 (first fixed: 9.4(5a))
- Release 10.3 and earlier (first fixed: 10.3(10))
- Release 10.4 (first fixed: 10.4(8))
- Release 10.5 (first fixed: 10.5(6))
- Release 10.6 (first fixed: 10.6(4))
- 8.3 and earlier — Migrate to a fixed release
- Release 8.4 (first fixed: 8.4(14))
- Release 16.0 and earlier (first fixed: 16.0(9h))
- Release 16.1 (first fixed: 16.1(6g))
- Release 16.2 (first fixed: 16.2(3g))
- 4.2 and earlier — Migrate to a fixed release
- Release 4.3 (first fixed: 4.3(6j) / 4.3(6.260049))
- Release 4.3(6.260059) (first fixed: 6.0 / 6.0(2e))
Official advisory · high-confidence parse· fetched 8 days ago·verify at source
- 9.4(5a)
- 10.3(10)
- 10.4(8)
- 10.5(6)
- 10.6(4)
- 8.4(14)
- 16.0(9h)
- 16.1(6g)
- 16.2(3g)
- 4.3(6j) / 4.3(6.260049)
- 6.0 / 6.0(2e)
Official advisory · high-confidence parse· fetched 8 days ago·verify at source
Mitigation checklist
- Upgrade to the first fixed release for your train per the Fixed Releases table in this advisory.
- Release 9.3 and earlier: migrate to a fixed release.
- Release 9.4: upgrade to 9.4(5a).
- Release 10.3 and earlier: upgrade to 10.3(10).
- Release 10.4: upgrade to 10.4(8).
- Release 10.5: upgrade to 10.5(6).
- Release 10.6: upgrade to 10.6(4).
- Release 8.3 and earlier: migrate to a fixed release.
- Release 8.4: upgrade to 8.4(14).
- There are no workarounds that address these vulnerabilities.
Official advisory · high-confidence parse· fetched 8 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.