# Network Device Patch Management and Firmware

Canonical: https://patchmanagementpolicy.com/patching/network-devices-and-firmware/
Last reviewed: 19 Nov 2026

## Network device patch management

Network vendors publish on stated schedules with exceptions. Cisco bundles FXOS and NX-OS advisories on the fourth Wednesday of February and August, IOS XR on the second Wednesday of March and September, and IOS and IOS XE on the fourth Wednesday of March and September. Fortinet uses the second Tuesday. Read 19 Nov 2026.

### Cisco: bundles and the conditions that break them

Cisco generally discloses advisories at 1600 GMT on a Wednesday and releases bundles twice a year for three product families. Its policy reserves the right to publish an individual advisory outside the schedule, and names the conditions: heightened public awareness of a serious vulnerability, learning of active exploitation, or coordinated disclosure with a third-party center ([Cisco Security Vulnerability Policy](https://sec.cloudapps.cisco.com/security/center/resources/security_vulnerability_policy.html)). The next bundle dates, computed from the rule, are 24 Feb 2027 (FXOS and NX-OS), 10 Mar 2027 (IOS XR) and 24 Mar 2027 (IOS and IOS XE).

The policy consequence is a two-lane rule: a planned review lane on the bundle dates, and an unscheduled lane triggered by a vendor out-of-cycle notice or a KEV addition.

The same rhythms appear in the calendar in [monitor for releases](https://patchmanagementpolicy.com/process/monitor-for-releases/), and the table of asset classes is at [patching by asset type](https://patchmanagementpolicy.com/patching/).

### Fortinet: which branches get a fix

| Fortinet severity (CVSS band) | Branches Fortinet says it fixes | Publication |
|---|---|---|
| Critical, 9.0 to 10.0 | All supported versions | Monthly or out-of-cycle advisory |
| High, 7.0 to 8.9 | All supported versions | Monthly advisory |
| Medium, 4.0 to 6.9 | Current and prior version | Monthly advisory |
| Low, 2.0 to 3.9 | Latest supported version | Monthly advisory |

Source: Fortinet PSIRT policy, read 19 Nov 2026. This is Fortinet's statement of its own practice; products with a rapid release cycle may be limited to the previous four minor versions.

Fortinet publishes on the second Tuesday of the month (next: 8 Dec 2026 and 12 Jan 2027, computed). The table matters for the window: a device on an older branch may have no fix for a medium issue and so needs an upgrade, not a patch. Plan the upgrade path in advance. Juniper's schedule could not be read from this environment on 19 Nov 2026 and is not described.

### Firmware and the window

NIST notes that some installations “require administrator privileges, such as installing firmware patches for a system basic input/output system,” and points to NIST SP 800-147 on BIOS updates. The usual constraint for a network device is an outage: a single gateway has no spare, so the window is set by when the business can lose it, and rollback is the previous image kept on the device or in a repository. Write those facts into the [maintenance group](https://patchmanagementpolicy.com/patching/) and the [maintenance windows clause](https://patchmanagementpolicy.com/policy-sections/maintenance-windows/).

### Evidence

- Image version per device and the advisory it addresses.
- The date a vendor bundle or out-of-cycle notice was received, and the date the device was fixed.
- Devices on end-of-support software, kept with the compensating controls from the exceptions record.

### Questions

**what is patch management in networking**

In networking it is the controlled upgrade of device software and firmware against vendor advisories. Cisco publishes bundles for IOS and IOS XE on the fourth Wednesday of March and September, and Fortinet publishes monthly on the second Tuesday, so the work follows both a calendar and unscheduled notices.

### Sources

- [Cisco Security Vulnerability Policy](https://sec.cloudapps.cisco.com/security/center/resources/security_vulnerability_policy.html), read 19 Nov 2026
- [Fortinet PSIRT policy](https://www.fortiguard.com/psirt_policy), read 19 Nov 2026
- [NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning (April 2022)](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-40r4.pdf), read 19 Nov 2026

Last reviewed 19 Nov 2026

### Related pages

- [Step 2: How to Track Vendor Patch Releases](https://patchmanagementpolicy.com/process/monitor-for-releases/)
- [Patch Maintenance Window Policy Clause](https://patchmanagementpolicy.com/policy-sections/maintenance-windows/)
- [Patching by Asset Type: Windows to OT Windows](https://patchmanagementpolicy.com/patching/)
- [Patch Management Policy Exceptions Clause Template](https://patchmanagementpolicy.com/templates/patch-exceptions-clause/)
