Cisco’s hardening releases ship a 9.8 without saying what the bug is
Cisco published 14 advisories on 7 October. Four were security hardening releases that collapse internally found flaws into one CVE per defect class. The per-feature advisories published the same day show what that costs anyone trying to scope exposure.

What the hardening releases say
On 7 October Cisco published its NX-OS Software Security Hardening Release for October 2026 [1]. It is rated critical at CVSS 9.8 and lists six CVEs. Each CVE stands for a class of defect rather than a single bug. CVE-2026-76455 sits at 9.8 for access control failures under CWE-284. CVE-2026-76459 sits at 9.8 for out-of-bounds writes under CWE-787. CVE-2026-76453 is 8.8 for improper neutralisation under CWE-707, and CVE-2026-76456, CVE-2026-76457 and CVE-2026-76458 are 8.6 for improper input validation, out-of-bounds reads and mishandled exceptional conditions [1]. The score against each CVE reflects the most severe underlying issue in that category. The advisory states that no workarounds address the vulnerabilities [1].
The affected list covers MDS 9000 multilayer switches, Nexus 3000, 7000 and 9000 series switches including ACI mode, UCS 6300, 6400, 6500 and 6600 fabric interconnects and the UCS X-Series Direct Fabric Interconnect 9108 100G. Cisco qualifies the list with the phrase that matters: vulnerable regardless of device configuration [1].
Two more advisories follow the same structure. The APIC hardening release lists CVE-2026-76498, CVE-2026-76499 and CVE-2026-76500, all at 9.8, mapped to CWE-284, CWE-707 and CWE-664, affecting APIC regardless of device configuration, with fixes in 6.0(9h), 6.1(6g) and 6.2(3g), releases 5.3 and earlier requiring migration, and no workarounds [2]. The Cisco License On-Prem hardening release, covering the product previously branded Smart Software Manager On-Prem, reaches CVSS 10.0: CVE-2026-76482 at 10.0 under CWE-347 for improper verification of a cryptographic signature, CVE-2026-76480 at 9.8 under CWE-306, CVE-2026-76483 at 9.1 under CWE-522 and CVE-2026-76484 at 8.8 under CWE-94. The fix is release 10-202609, and 9-202601 and earlier must be migrated [3].
All three attribute discovery to Cisco’s internal security testing, carried out with existing testing processes and frontier AI models, and state that Cisco’s product security incident response team is not aware of public announcements or malicious use [1][2][3].
What the per-feature advisories say instead
The same publication cycle produced advisories built the opposite way. The NGOAM advisory for Nexus 3000 and 9000 switches in standalone NX-OS mode names three CVEs and states the precondition for each. CVE-2026-76485 requires only that NGOAM is enabled. CVE-2026-76486 additionally requires SRv6, or NV Overlay with a VXLAN EVPN VNI mapped to an NVE interface that has at least one learned peer tunnel endpoint. CVE-2026-76501 requires SRv6 [4]. The advisory supplies the commands to check each condition, lists the platforms confirmed not vulnerable, and notes that Nexus 3000 switches do not support SRv6 and only a subset of Nexus 9000 models do [4].
Reporting on the cycle reproduced that detail. NX-API and MPLS OAM are disabled by default on the affected switches, Nexus 7000 and ACI-mode Nexus 9000 are not affected by the feature-gated flaws, and Nexus 9000 models using Silicon One ASICs cannot enable MPLS OAM [6][7]. CVE-2026-76471 is a heap overflow reached through NX-API, rated 9.8 on Nexus and high on UCS 6300 fabric interconnects, where exploitation requires valid low-privileged credentials through the UCS Manager XML API, which is enabled by default; UCS 4.3 is fixed in 4.3(6j) and 4.2 and earlier must be migrated [8].
Published scores differ. eSecurity Planet reports all five feature-gated NX-OS CVEs at 9.8 while also noting the high rating for the UCS 6300 case, and does not reconcile the two [7]. SOCRadar lists the same five at 9.8 and flags the inconsistency explicitly [9]. BleepingComputer describes the five as critical and publishes no scores for them [6]. Cybersecurity News reports the NGOAM advisory’s 9.8 base score without stating whether it applies to each CVE individually [10]. The vendor advisory carries a single base score for the advisory rather than per CVE [4], which is where the divergence originates.
Why the difference matters for triage
A feature-gated advisory can be triaged against a configuration. Run the feature checks, confirm the release, and a switch is either in scope or it is not. A CWE bucket cannot be triaged that way. There is no feature flag, no precondition and no description of the defect, so the only scoping variables left are platform and software train, and the advisory has already said the platform is affected regardless of configuration [1][2]. The hardening releases therefore convert into fleet-wide upgrade work. The per-feature advisories convert into a short list.
This is a standing condition rather than a one-off. The advance notification issued on 30 September and finalised on 7 October describes hardening releases and other security advisories as scheduled for the first and third Wednesday of each month, lists 14 advisories for 7 October with severities running from 10.0 down to 4.4 across NX-OS, APIC, License On-Prem, Meraki and Finesse, and warns that the schedule is not a final commitment and that products may be added or rescheduled [5].
Fix availability across the cycle is uneven. The Canadian Centre for Cyber Security’s summary of the same advisories lists affected version strings across Nexus 3000 and 9000, Meraki campus gateways, cellular gateways, access points, switches, cameras and security appliances, UCS software, APIC, Finesse and the contact centre products, with several fixed releases dated to late October and mid-November 2026 and others to January and February 2027 [11]. Part of what was disclosed on 7 October has no fix available yet.
What to do this week
- Build the exposure list for the hardening releases on platform and software train, not on enabled features. Configuration does not reduce scope for the bucketed CVEs [1][2].
- Run the feature checks for the gated CVEs and record the result per device, so the short list is defensible: NGOAM, NX-API, MPLS OAM, SRv6 and NV Overlay state [4][7].
- Use Cisco’s software checker per platform and train rather than assuming one fixed version across a fleet; the advisories do not publish fixed releases inline [6][9].
- Treat the Live Protect shields issued for the feature CVEs, available through the NX-OS 10.6(3) download page, as a stopgap while upgrades are scheduled, not as remediation [4][9].
- Disable NGOAM, NX-API or MPLS OAM where operations do not require them, after assessing impact. Cisco describes disabling NGOAM as removing the attack vector while simultaneously stating that no workarounds exist, and says the step was lab-tested only [4].
- For Cisco License On-Prem, read the release string first. On 9-202601 and earlier the action is migration, not patching, and the Smart Licensing Utility is confirmed unaffected [3].
- Treat unexplained process crashes and device reloads on feature-enabled switches as potential security events until investigated, and correlate NX-API HTTP activity and configuration changes against out-of-band management telemetry [9].
The offensive security reading
Nothing in this cycle is being exploited as far as Cisco or the reporting shows [1][4][6][9]. The exposure is administrative. A bucketed advisory is cheaper to publish than six individual ones, and it moves the scoping work to the operator, who holds less information than the vendor and has fewer ways to narrow the question. Where the vendor also records no workaround, the only remaining lever is the upgrade schedule.
The discovery note is worth reading twice. Cisco says these findings came out of internal testing assisted by frontier AI models [1][2][3]. Bulk internal discovery produces more findings than a per-bug disclosure process can carry, and the category-level advisory is the predictable output. Expect more of them on the first and third Wednesday of each month [5]. Fleets inventoried by release train and platform will absorb that cadence. Fleets inventoried by feature will find that the feature list no longer answers the question.
Sources
Every R3KONX article cites its primary material. 11 sources, in order of first citation. Links open the original publication.
- Cisco NX-OS Software Security Hardening Release: October 2026 (cisco-sa-hardening-nxosw1-cWzSbtR) Cisco Security Advisories · 2026-10-07
- Cisco Application Policy Infrastructure Controller Security Hardening Release: October 2026 (cisco-sa-hardening-apic-UOXWtfh) Cisco Security Advisories · 2026-10-07
- Cisco License (Smart Software Manager) On-Prem Security Hardening Release: October 2026 (cisco-sa-hardening-ssm-Ph77wdhf) Cisco Security Advisories · 2026-10-07
- Cisco Nexus 3000 and 9000 Series Switches NGOAM Remote Code Execution Vulnerabilities (cisco-sa-ngoam-rce-LWKQ4BU) Cisco Security Advisories · 2026-10-07
- Cisco Advance Notification for Publication of October 7, 2026, Security Advisories (cisco-sa-notice-fBn58ELx) Cisco · 2026-09-30
- Cisco warns of critical flaws allowing Nexus switch takeover BleepingComputer · 2026-10-08
- Five Critical Cisco Nexus Flaws Could Grant Root Access: What to Check eSecurity Planet · 2026-10-08
- Cisco fixes critical NX-OS remote code execution vulnerability Field Effect · 2026-10-09
- Critical Cisco NX-OS Flaws Threaten Nexus Switches SOCRadar · 2026-10-09
- Critical Cisco Nexus Flaws Let Unauthenticated Attackers Execute Code With Root Privileges Cyber Security News · 2026-10-08
- Cisco security advisory (AV26-1020) Canadian Centre for Cyber Security · 2026-10-08
Researched and written by the R3KONX analysis desk from the cited primary material. Published CVSS scores for the feature-gated NX-OS vulnerabilities differ between sources; where they diverge both readings are given. No fixed release is asserted beyond what the vendor advisories state. Corrections to event@r3konx.asia.
