Skip to content
Zero Day Playbook

A mitigation buys hours, not a fix, so pick the cheapest one that closes the path and prove it took

Ten mitigations from 2026 advisories, what each costs and how to prove it took

NIST SP 800-40 Rev. 4, section 3.3, describes emergency mitigation as the procedure "to temporarily mitigate vulnerabilities before a patch is available", and section 3.5.3 adds that "Schedules should be set and enforced for both patch deployment and mitigation removal." In this guide a mitigation lowers the chance of exploitation without fixing the flaw. Every row below comes from a vendor advisory or a record read on 19 Nov 2026, and the vendor is named where the claim is the vendor's. The verification column is the check to run after the change, from the device and from outside. The owner column names the role that makes the change and signs the check.

Scroll the table sideways for more columns

TypeReal exampleWhat it costsHow to verify it tookOwner
Restrict the interfacePAN-OS CVE-2026-0322, 14 Oct: limit the management interface to a jump box (Palo Alto advisory CVE-2026-0322)Admins and scripts must come through that hostRead Device > Setup > Interfaces > Management Interface Settings > Permitted IP Addresses. Test the management address from an untrusted network and expect no answerNetwork owner
Disable the featureFortiMail CVE-2026-104286, 1 Oct: turn off the IBE service (Fortinet)IBE secure mail stops; recipients cannot open or reply through the portalRead Encryption > IBE > IBE Service in the GUI, or the status line under config system encryption ibe in the CLIMessaging service owner
Remove a permissionScreenConnect CVE-2026-84869, 3 Sep interim advisory (the bulletin and 26.6.5 followed on 8 Sep): deselect TransferFiles in every role (ConnectWise)Technicians cannot transfer files in sessionsOpen Administration > Security > Roles and check each session group in each role; the permission shows in bold when setRemote support service owner
Remove a settingCisco ASA and FTD CVE-2026-76418, 28 Oct: remove secondary authentication (Cisco)The VPN loses its second credential, which Cisco says lowers its security postureshow running-config tunnel-group must show no secondary-authentication-server-group in any group, including DefaultWEBVPNGroupNetwork security owner
Filter at a proxy or WAFAtlassian CVE-2026-21589, 5 Oct: block URLs with two dots beside a slash, backslash or double colon (Atlassian)Rule upkeep and false positives; on Confluence, Jira and the others a restart of every nodeFrom outside, request a harmless URL carrying an encoded ../ segment and confirm the proxy or the rewrite rule answers, not the applicationPlatform team that runs the proxy
Take it off the internetAtlassian CVE-2026-21589: remove the instance from the internet until patched (Atlassian); PHP CVE-2026-109618: CISA says take unpatchable systems offlineExternal users and integrations lose accessFrom a network outside yours, confirm the address no longer answers on its portNetwork owner, service owner informed
Limit the network pathTomcat CVE-2026-34486: restrict the cluster receiver port to the other cluster nodes (Tomcat clustering guide)A node added later needs a new ruless -ltnp shows the receiver (default port 4000, up to 4100 with autoBind). From a non-member host, a connection to it must failApplication platform owner
Set a secretArtifactory CVE-2026-82329, 28 Aug: add your own additionalJoinKeys value (JFrog)A restart of the Access service; the new key must be kept as secret as the join keyConfirm the entry in system.yaml, or JF_SHARED_SECURITY_ADDITIONALJOINKEYS in containers, and that the Access service restarted after the editArtifact repository service owner
Change configurationOpenSSH CVE-2026-123158, 5 Nov: PasswordAuthentication no, set in sshd_config including inside Match blocks (OpenSSH, Alpine)Nobody can log in with a password; existing sessions keep running through the restartsshd -t, restart sshd, then sshd -T | grep -i passwordauthentication must print no. Test key login in a second session firstOS owner for the host
Block a kernel moduleLinux CVE-2026-46300: stop esp4 and esp6 from loading (Red Hat)IPsec stops after the next rebootlsmod | grep -E 'esp4|esp6' prints nothing, and /etc/modprobe.d/dirtyfrag.conf holds the install lines. Check lsmod first: if neither is loaded, IPsec is not in useOS owner for the host

Some mitigations are partial, and the vendor says so

PHP's advisory for PHP2Shell, CVE-2026-109618, lists memory_limit=-1 as an interim step and says it is not complete, because a failed mmap() can still reach the vulnerable path. PHP calls the upgrade the only complete mitigation. Verify the value from inside a worker, not from php.ini: ini_get('memory_limit') in a private test script must return -1, because a pool, directory or application setting can restore a finite limit.

Palo Alto lists no workaround for CVE-2026-0322. The jump-box restriction is hardening: the flaw stays and the rating moves from CVSS 4.0 8.6 to 8.5, because the attack vector becomes adjacent. Palo Alto calls its Threat Prevention signatures, Threat IDs 510046 and 510047, limited coverage: they work only when management traffic is routed through a data-plane interface with certificate replacement and decryption. Cisco prefers the upgrade to its ASA mitigation and says the mitigation was proven in a test environment, so check it in yours. F5 lists one workaround for CVE-2026-94127, an iRule available on request, and does not say what it changes; test it on a non-production unit.

A third-party note is not a vendor claim. Medcrypt reports that MaxAuthTries 1 keeps password login working while blocking its reproduction of the OpenSSH bypass and that MaxAuthTries 2 does not. It is a stopgap, and a user who mistypes a password once is disconnected.

Some advisories offer none. Broadcom for ESX CVE-2026-41709 and Citrix for CVE-2026-19490 list no workaround, so the patch is the only fix they offer.

Worked case: OpenSSH on Alpine, public events and a constructed team's hours

All times are UTC. The public events are real. The team is constructed to show the order of work: it is the invented fleet of where a new CVE hits you, where checks cut 120 Linux hosts to nine in scope, four reachable from the internet and five internal. The mitigation clock starts when the fix goes public, not when a CVE ID exists. The ID, CVE-2026-123158, was published at 15:46 UTC on 5 Nov, 6 hours 46 minutes after the fix. A team that waited for the ID to start would have lost that time.

Scroll the table sideways for more columns

WhenHours after the fixPublic eventConstructed team's stepOwner
5 Nov, 09:000OpenSSH fix pushed to the public repository at 09:00; 10.6p2 released at 09:01; Alpine publishes its advisory and fixed packagesNot yet seenNone
5 Nov, 11:002 hAnalyst reads the Alpine post, opens the decision log and declares the event: the fix is public and the flaw is an authentication bypassAnalyst on duty, then event lead
5 Nov, 11:00 to 12:302 h to 3 h 30 minScope: the five checks run across the fleet; nine hosts in scope; exposure sorted into four internet and five internalPlatform lead
5 Nov, 12:30 to 13:153 h 30 min to 4 h 15 minMitigate: PasswordAuthentication no on the four internet-facing hosts, key login tested in a second session firstPlatform lead, change approver informed
5 Nov, 13:164 h 16 minExploit code appears on GitHub (GreyNoise timeline, 13:16:55 UTC)Verify: sshd -T on the four hosts prints no. Board brief 1 says four of four internet hosts mitigated, five internal in progressPlatform lead; scribe logs
5 Nov, 14:305 h 30 minAll nine hosts mitigated and verified; costs logged with an expiry of 7 Nov, 12:00Platform lead
5 Nov, 15:466 h 46 minCVE-2026-123158 published (GreyNoise timeline, 15:46:25 UTC)The CVE ID is added to the log and the briefScribe
6 Nov, 09:0024 hPatch: apk upgrade -U -a on one canary host, then the four internet hosts, then sshd restarted with rc-service sshd restart, because Alpine says the package upgrade alone does not replace the running daemon; apk info -v openssh-server confirms the fixed packagePlatform lead
6 Nov, 14:0029 hPatch the five internal hosts and verifyPlatform lead
6 Nov, 16:0031 hRemove: PasswordAuthentication returns to the baseline where password login is needed; removal logged after apk info -v openssh-server confirmed the fixed packagePlatform lead
7 Nov, 00:4639 h 46 minGreyNoise sees the first successful exploitation on one of its sensorsAll nine hosts patched and the mitigation closed 8 h 46 min earlierEvent lead closes the event
9 NovAbout 4 daysCISA adds the CVE to KEV, due 12 NovNothing openNone

Give every mitigation an owner, a review time and a removal condition

The owner is a name, taken from the role in the table above. The review time is a clock time, no later than the next vendor update, since vendors revise advisories: Fortinet revised FG-IR-26-175 on 5 and 7 Oct 2026, and SonicWall updated its workaround on 9 Nov 2026. The removal condition is the fix, verified by version check or rescan.

Tell support about the user-visible cost before it ships. Run a new WAF rule in log-only mode for an hour on a low-risk group if the exposure allows. If exploitation is active and the service is exposed, enforce first and loosen later.

One mitigation must be in place before the patch, not after. WordPress 7.1.4's updater still creates a predictable folder under wp-content/upgrade while it installs the fix, so deny web access to that directory first (nginx: location ^~ /wp-content/upgrade/ { deny all; }; Apache: Require all denied). WordPress.org names no workaround; this rule follows from the 7.1.4 code change, which adds an index.php to that folder.

A mitigation does not remove access the attacker already has

Mitigations close a path from now on. FortiMail's KEV entry marks forensic triage as Yes, so preserve the logs and a configuration backup before you change the appliance. Artifactory shows the limit most clearly: patching does not revoke issued tokens, and Wiz reports that attacker Groovy plugins and stolen Access signing keys survive an upgrade, so the join-key workaround cannot undo an intrusion from before it was set. Until the fix is verified and the hunt is done, the board line reads open, with the mitigation named and its expiry.

Sources

  1. Fortinet PSIRT advisory FG-IR-26-175, read 19 Nov 2026
  2. FortiMail CLI reference, system encryption ibe, read 19 Nov 2026
  3. Palo Alto Networks advisory CVE-2026-0322, read 19 Nov 2026
  4. Cisco advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75, read 19 Nov 2026
  5. Atlassian advisory CVE-2026-21589, read 19 Nov 2026
  6. ConnectWise ScreenConnect security bulletin, 8 Sep 2026, read 19 Nov 2026
  7. ConnectWise advisories page, read 19 Nov 2026
  8. JFrog security advisories, CVE-2026-82329 section and workaround, read 19 Nov 2026
  9. F5 advisory K000162605, read 19 Nov 2026
  10. PHP security advisory GHSA-w8hw-w9fx-j79w, read 19 Nov 2026
  11. CISA alert, Critical Vulnerabilities in PHP Require Immediate Patching, read 19 Nov 2026
  12. Alpine Linux advisory, OpenSSH password authentication bypass, 5 Nov 2026, read 19 Nov 2026
  13. OpenSSH 10.6p2 release notes, read 19 Nov 2026
  14. Medcrypt, independent reproduction and mitigation guidance for CVE-2026-123158, read 19 Nov 2026
  15. GreyNoise event page and timeline for CVE-2026-123158, read 19 Nov 2026
  16. Apache Tomcat 11 clustering guide, read 19 Nov 2026
  17. Red Hat security bulletin RHSB-2026-003, read 19 Nov 2026
  18. Broadcom security advisory VMSA-2026-0006, read 19 Nov 2026
  19. WordPress 7.1.4 security release note, read 19 Nov 2026
  20. WordPress core source, 7.1.4 tag, class-wp-upgrader.php, read 19 Nov 2026
  21. Wiz Research, Artifactory exploitation report, 10 Sep 2026, read 19 Nov 2026
  22. SonicWall PSIRT advisory SNWLID-2026-0014, read 19 Nov 2026
  23. Citrix security bulletin CTX696939, read 19 Nov 2026
  24. CISA KEV feed, catalog version 2026.11.18, read 19 Nov 2026
  25. CISA KEV entry for CVE-2026-104286, read 19 Nov 2026
  26. NVD record for CVE-2026-123158, read 19 Nov 2026
  27. NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning, read 19 Nov 2026

Last reviewed 19 Nov 2026.