Security

Patch-Week Fatigue: Fortinet, Cisco, Citrix, and a Microsoft Emergency Fix

Leave a comment

It was one of those weeks where the patch list got longer than the day. I am not going to walk through bugs or tell you how to exploit anything. The useful part is triage: what to do first, and who actually needs to move.

Fortinet published a huge set of advisories, SecurityWeek reported, covering nearly 100 vulnerabilities, about 17 of them critical, a few weeks after the company said it had added frontier AI models to its product security testing. FortiMail took a lot of the critical fixes, with FortiAuthenticator, FortiOS, FortiManager, FortiAnalyzer, FortiSASE, and FortiClient in the mix as well. Fortinet had not reported exploitation of those bugs. If you have Fortinet gear, especially anything internet-facing, this is a start-with-the-critical-advisories week, not a “we’ll catch the next maintenance window” week.

Cisco BroadWorks was a different shape of urgency. CISA had already added CVE-2026-20320 to its Known Exploited Vulnerabilities catalog, and the patch has been out since August. Cisco later updated the advisory to say it does not have direct evidence of active exploitation, even as the KEV listing stands, and that there are no workarounds. If you run BroadWorks, the action is still the same: apply the fixed software for the train you actually use. Citrix, in the same stretch, patched a large set of NetScaler ADC and Gateway flaws, including 10 rated critical, plus a separate critical fix for NetScaler Console. Citrix had not reported exploitation either, but NetScaler bugs do not stay quiet once patches are out. If you run it, this was a patch-now day.

Then Microsoft had to ship emergency out-of-band updates to fix Windows activation and licensing failures caused by this month’s security updates. That one hits organizations that use SLMGR to automate activation. Already-activated devices stay activated, and shops that already have the KMS client key in place and do not need the affected Slmgr.vbs commands are not expected to be in the blast radius. The November printing issue I wrote about earlier is a separate problem, and I have not seen a matching emergency patch for that one.

My take

My triage habit is boring on purpose. Known-exploited and internet-facing first. Then the emergency fix if you are actually in the population it was written for. Then the rest of the pile, after you have read the vendor notes and staged it somewhere you can afford to break. A week like this rewards a list and a calendar, not heroics, and it is not over until the leftover November bugs get their own fixes.

God Bless, and May the Source Be with You!

References & Further Reading

Subscribe (RSS) Follow News via RSS

Leave a note

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.