# Run an out-of-band patch in rings, with a rollback that keeps the mitigation in place

Guide, 19 Nov 2026, read 19 Nov 2026

**The short answer.** An out-of-band patch is a fix applied outside the maintenance calendar because exploitation will not wait. Run it with a named approver, a smoke test the application owner wrote, small rings and a rollback that keeps any mitigation. JFrog's Artifactory flaw went from advisory on 28 Aug 2026 to about 406,000 attempts a day by 2 Sep.

## Go out of band when the calendar is slower than the attacker

NIST SP 800-40 Rev. 4 defines enterprise patch management as "the process of identifying, prioritizing, acquiring, installing, and verifying the installation of patches, updates, and upgrades throughout an organization." An out-of-band patch runs that process outside the calendar, so every part of it has to exist before the day it is needed.

CISA's BOD 26-04 builds its federal deadlines from four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an attacker can automate the exploit, and the technical impact. The directive says that of the two events that can start a timeline, "Whichever event occurs first starts the remediation timeline." Deadlines in the KEV entries this site holds are not uniform, so read the due date of each one.

Some flaws arrive already exploited. Microsoft marked the Windows AFD flaw CVE-2026-68820 as exploited on 11 Aug 2026, the day it published the fix, and CISA listed it the same day. PHP2Shell was earlier still: Fastly saw the first request from a PHP2Shell-named tool at 03:59 UTC on 21 Oct 2026, 10 hours 1 minute before PHP's coordinated release at 14:00 UTC.

| CVE | Added to KEV | KEV due date | Days allowed |
| --- | --- | --- | --- |
| CVE-2026-82329, Artifactory | 2 Sep 2026 | 5 Sep 2026 | 3 |
| CVE-2026-0322, PAN-OS | 14 Oct 2026 | 17 Oct 2026 | 3 |
| CVE-2026-76418, Cisco ASA and FTD | 29 Oct 2026 | 1 Nov 2026 | 3 |
| CVE-2026-123158, OpenSSH | 9 Nov 2026 | 12 Nov 2026 | 3 |
| CVE-2026-111497, Node.js and Brotli | 27 Oct 2026 | 10 Nov 2026 | 14 |
| CVE-2026-41709, VMware ESX | 28 Oct 2026 | 11 Nov 2026 | 14 |
| CVE-2026-19868, SonicWall SonicOS | 6 Nov 2026 | 20 Nov 2026 | 14 |

## Name the approver, the deputy and the owner of each gate before the day

The change record needs four entries: the advisory link as read, the scope, the rollback and the owner of the smoke test. The approver has emergency change authority, so the change board is not a gate; name the approver, a deputy and the channel in advance. The application owner holds what platform engineering lacks: which login, checkout or API call proves the service works.

## Write the smoke test and the rollback first, then widen in rings

A smoke test runs in under ten minutes and ends in a pass or a fail that anyone on call can read. A rollback is a snapshot of the host or volume together with its database, a previous image tag, or a pinned previous package. Take it before ring 0, and try it once on ring 0 hosts.

A rollback of a security fix puts the flaw back. If the vendor gave a mitigation, apply it to the hosts first and keep it through a rollback, so the rolled-back host is still closed. Where no mitigation exists, a rollback is a decision for the approver, taken with the exposure in front of them.

Keep rings small enough to roll back. The first ring is one or two hosts that carry real traffic and have owners who answer the phone.

| Ring | Scope | Hold | Pass condition |
| --- | --- | --- | --- |
| 0 | Staging, or two hosts that carry real traffic | 30 minutes | Service starts, smoke test passes, version shows the fixed build |
| 1 | About ten percent of exposed hosts | 1 hour | Error rate and latency match the baseline of the previous hour |
| 2 | All other exposed hosts | Until each host is verified | Smoke test passes, fixed build recorded per host |
| 3 | Internal hosts | Same day | Fixed build recorded, rescan clean |

## Plan for what must restart, and for versions with no fix

An upgrade that leaves the old process running has not fixed anything. Check the start time of the running process against the install time: on Linux, ps -o lstart= -p $(pgrep -o sshd) prints when the oldest sshd started.

Some versions get no patch. PHP 8.1 and older receive no upstream fix, and the Node.js advisory covers only the 22, 24 and 26 lines, so 20.x, 23.x and 25.x need a move to a supported line. Fortinet tells FortiMail 7.0 users to migrate to a fixed release. For such hosts the answer is the vendor mitigation or taking the host offline, which is what CISA's alert advises for PHP versions that cannot be updated.

| Product and CVE | What restarts | Source note |
| --- | --- | --- |
| OpenSSH on Alpine, CVE-2026-123158 | rc-service sshd restart; existing sessions keep running | Alpine: upgrading alone does not replace the running daemon |
| PHP, CVE-2026-109618 | Every PHP worker | PHP: a restart and regression testing for a minor release |
| Node.js, CVE-2026-111497 | Rebuild images, then restart processes | Node.js advisory; copies of Brotli outside Node.js need their own upgrade |
| Apache Tomcat cluster, CVE-2026-34486 | Each node, as a rolling restart if sessions replicate | Tomcat 11.0.21, 10.1.54 or 9.0.117 or later |
| Linux kernel, CVE-2026-46300 | Reboot, or kpatch where Red Hat ships it | Red Hat offers kpatch for some streams |
| VMware ESX, CVE-2026-41709 | Maintenance mode and a reboot per host | Broadcom: plan vMotion or a rolling cluster update |
| FortiMail, CVE-2026-104286 | Reboot, with a mail-flow interruption | Fortinet: back up the configuration first |
| ScreenConnect, CVE-2026-84869 | Host clients are reinstalled and access agents updated | ConnectWise: the server upgrade does not update technician clients |

## Worked case: Artifactory from 28 Aug to 31 Aug 2026

CVE-2026-82329 let an unauthenticated caller obtain an administrator token from the Artifactory Access service on a default install, where the join key is empty. The CNA's CVSS base score is 9.8. JFrog published six fixed builds on 28 Aug 2026, a Friday: 7.111.21, 7.117.28, 7.125.20, 7.133.29, 7.146.38 and 7.161.20.

Fastly saw no exploitation on 28 Aug and only single-digit probes on 29 and 30 Aug. On 31 Aug it recorded about 75,000 requests, nearly 98 percent from offensive-security services. A public exploit appeared on 1 Sep, with about 171,000 attempts. On 2 Sep, when CISA listed the CVE, attempts peaked near 406,000. The KEV due date was 5 Sep.

The schedule below is built from those dates. Patching ends on 30 Aug, before the Monday wave, and Monday is verification. The KEV due date of 5 Sep is the outer limit, not the plan.

- 28 Aug, hour 0: list every self-hosted instance and read GET /artifactory/api/system/version on each. Match each to its train and fixed build. 7.146.37 is not enough; JFrog's affected range ends at 7.146.36 but NVD treats everything below 7.146.38 as affected. Look for additionalJoinKeys under shared, security in system.yaml.
- Hour 2: on instances reachable from the internet, apply JFrog's workaround. Generate a key with openssl rand -hex 16, add it as additionalJoinKeys, keep the existing joinKey, and restart the Access service. The existing key keeps working, so cluster peers are unaffected. The mitigation also stays in place if a later upgrade is rolled back.
- Hour 4: ring 0, the staging instance, to the first fixed build for its train. Smoke test: the version endpoint shows the build, one CI job deploys and resolves a small artifact with a real service token, and a second cluster node rejoins with the existing join key.
- 29 Aug: ring 1, one production instance serving the team with the lowest release pressure, held for an hour. 30 Aug: ring 2, all other instances, one per train at a time.
- 31 Aug: verify the version on every instance. Then run the hunt in the compromise assessment guide (Compromise assessment after patching) for the window from 28 Aug.
- Same day: patching does not revoke tokens already issued. Rotate the platform join key and revoke access tokens issued since 28 Aug.

## Close the change with someone who did not deploy it

Close an out-of-band change only when a second person, or the scanner, has read the fixed version on each asset. A deployment log shows that a command ran, not what is running. List assets still open with an owner and a date, and remove each temporary mitigation after the check, with the removal logged.

Patching changes the code, not what an attacker already took. ConnectWise told all partners on 13 Nov 2026 to verify that every technician client runs 26.6.5 or later, because updating the console does not update clients. Where the CVE is in the KEV catalog with forensic triage marked Yes, as FortiMail's is, preserve the appliance logs and a configuration backup before changing the appliance.

Keep for the auditor: the change number, approver, the advisory text as read with its URL and read date, the ring plan, the smoke test result per ring, the fixed build per asset, the verification output, and a time for each step. The same record feeds the 72-hour review.

## Related pages

- [The board brief by noon: template, interim note and a filled brief for Cisco ISE](/guides/board-brief-by-noon/)
- [What to do when a zero day is disclosed: the first four hours, worked on PHP2Shell](/guides/what-to-do-when-a-zero-day-is-disclosed/)
- [Zero day vulnerability defined: the sources, the tests and six 2026 cases](/guides/zero-day-vulnerability-defined/)

## Sources

- NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning: https://csrc.nist.gov/pubs/sp/800/40/r4/final (read 19 Nov 2026)
- CISA BOD 26-04, Prioritizing Security Updates Based on Risk: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- JFrog security advisories, CVE-2026-82329 section and workaround: https://docs.jfrog.com/releases/docs/jfrog-security-advisories (read 19 Nov 2026)
- Fastly Security Research, Artifactory exploitation activity, 3 Sep 2026: https://www.fastly.com/blog/cve-2026-82329-jfrog-artifactory-authentication-bypass-exploitation-activity (read 19 Nov 2026)
- JFrog documentation, Get Artifactory Version API: https://docs.jfrog.com/administration/reference/getartifactoryversion (read 19 Nov 2026)
- Microsoft MSRC CVRF, August 2026 release: https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Aug (read 19 Nov 2026)
- Microsoft MSRC record for CVE-2026-68820: https://api.msrc.microsoft.com/sug/v2.0/en-US/vulnerability/CVE-2026-68820 (read 19 Nov 2026)
- Fastly report on PHP2Shell exploitation and disclosure timeline: https://www.fastly.com/blog/how-fastly-detected-and-built-a-coordinated-response-to-php2shell (read 19 Nov 2026)
- CISA alert, Critical Vulnerabilities in PHP Require Immediate Patching: https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching (read 19 Nov 2026)
- PHP security advisory GHSA-w8hw-w9fx-j79w: https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w (read 19 Nov 2026)
- Alpine Linux advisory, OpenSSH password authentication bypass, 5 Nov 2026: https://alpinelinux.org/posts/2026-11-05-openssh-password-authentication-bypass/ (read 19 Nov 2026)
- Node.js security releases, 21 Oct 2026: https://nodejs.org/en/blog/vulnerability/october-2026-security-releases (read 19 Nov 2026)
- Apache Tomcat 11 security page: https://tomcat.apache.org/security-11.html (read 19 Nov 2026)
- Red Hat CVE page for CVE-2026-46300: https://access.redhat.com/security/cve/CVE-2026-46300 (read 19 Nov 2026)
- Broadcom security advisory VMSA-2026-0006: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/38017 (read 19 Nov 2026)
- Fortinet PSIRT advisory FG-IR-26-175: https://fortiguard.fortinet.com/psirt/FG-IR-26-175 (read 19 Nov 2026)
- ConnectWise ScreenConnect security bulletin, 8 Sep 2026: https://www.connectwise.com/company/trust/security-bulletins/2026-09-08-screenconnect-bulletin (read 19 Nov 2026)
- ConnectWise advisories page: https://www.connectwise.com/company/trust/advisories (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-82329: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-82329 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-0322: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0322 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-76418: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-76418 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-123158: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-123158 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-111497: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-111497 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-41709: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41709 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-19868: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-19868 (read 19 Nov 2026)
- CISA KEV entry for CVE-2026-68820: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-68820 (read 19 Nov 2026)
- NVD record for CVE-2026-82329: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-82329 (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://zerodayplaybook.com/guides/out-of-band-patch/
