# The network edge appliance playbook for the first 72 hours

Playbook, sources read 19 Nov 2026

**The short answer.** Firewalls, VPN gateways and other internet-facing appliances sit in the traffic path, and CISA added the PAN-OS flaw CVE-2026-0322 to KEV on the day Palo Alto disclosed it. This playbook gives the hour-by-hour order, the fixed builds for all five PAN-OS trains, the SonicOS firmware, the exposure checks and the no-fix branch.

An edge appliance is a closed box that sits where traffic enters. Flaws in it are usually exploited through the management interface or the VPN portal. In PAN-OS CVE-2026-0322 the attacker needs network reach to the management interface and a valid high-privilege account (CVSS 4.0 privileges required: high, base score 8.6), and a successful attack runs code as root. The attacker then holds the device that sees, decrypts and routes your traffic, plus the credentials, certificates and VPN sessions stored on it. No EDR agent runs on most of these boxes, so you cannot rely on endpoint telemetry to tell you what happened.

Patching is harder than on a server. The device is in the traffic path, so every upgrade is an outage unless you run a high-availability pair. Hotfix builds are cut per release train, so the fixed build depends on your minor release: PAN-OS CVE-2026-0322 has fixes in five trains and 20 builds, listed below. The exploit often needs a condition you can read from the device, such as a reachable management interface or SAML on the SSLVPN, so the first hours go to finding which boxes meet it. This page also covers other internet-facing services, because the same order applies: cut reachability, patch, then look for earlier access.

PAN-OS CVE-2026-0322 fixed builds, one line per release train (affected range, then the build to upgrade to). Cloud NGFW and Prisma Access are not affected, and every older unsupported PAN-OS version is affected and must move to a supported fixed version.

PAN-OS 12.2. 12.2.0 to 12.2.3: upgrade to 12.2.4 or later.

PAN-OS 12.1. 12.1.8 up to, not including, 12.1.10-h2: upgrade to 12.1.10-h2 or later; 12.1.5 up to, not including, 12.1.7-h8: upgrade to 12.1.7-h8, or 12.1.10-h2 or later; 12.1.2 up to, not including, 12.1.4-h12: upgrade to 12.1.4-h12, or 12.1.10-h2 or later.

PAN-OS 11.2. 11.2.14 to 11.2.15: upgrade to 11.2.16 or later; 11.2.11 up to, not including, 11.2.13-h3: upgrade to 11.2.13-h3, or 11.2.16 or later; 11.2.8 up to, not including, 11.2.10-h15: upgrade to 11.2.10-h15, or 11.2.16 or later; 11.2.5 up to, not including, 11.2.7-h21: upgrade to 11.2.7-h21, or 11.2.16 or later; 11.2.0 up to, not including, 11.2.4-h22: upgrade to 11.2.4-h22, or 11.2.16 or later.

PAN-OS 11.1. 11.1.14 up to, not including, 11.1.16-h3: upgrade to 11.1.16-h3 or later; 11.1.11 up to, not including, 11.1.13-h15: upgrade to 11.1.13-h15, or 11.1.16-h3 or later; 11.1.8 up to, not including, 11.1.10-h35: upgrade to 11.1.10-h35, or 11.1.16-h3 or later; 11.1.7 up to, not including, 11.1.7-h11: upgrade to 11.1.7-h11, or 11.1.16-h3 or later; 11.1.5 up to, not including, 11.1.6-h39: upgrade to 11.1.6-h39, or 11.1.16-h3 or later; 11.1.0 up to, not including, 11.1.4-h37: upgrade to 11.1.4-h37, or 11.1.16-h3 or later.

PAN-OS 10.2. 10.2.17 up to, not including, 10.2.18-h12: upgrade to 10.2.18-h12 or later; 10.2.14 up to, not including, 10.2.16-h11: upgrade to 10.2.16-h11, or 10.2.18-h12 or later; 10.2.11 up to, not including, 10.2.13-h26: upgrade to 10.2.13-h26, or 10.2.18-h12 or later; 10.2.8 up to, not including, 10.2.10-h41: upgrade to 10.2.10-h41, or 10.2.18-h12 or later; 10.2.0 up to, not including, 10.2.7-h38: upgrade to 10.2.7-h38, or 10.2.18-h12 or later.

SonicOS CVE-2026-19868 (SonicWall advisory SNWLID-2026-0014). Gen7 firmware 7.3.3-7015 and older: upgrade to 7.3.4-7013 or higher. Gen8 firmware 8.2.2-8015 and older: upgrade to 8.2.3-8015 or higher. NVD's data uses slightly different cut-offs, so follow SonicWall's figures: 8.2.2-8015 is still affected. The flaw is a SAML bypass in the SSLVPN, exploited per CISA's KEV entry; the dates are in the case table.

## The steps, hour by hour

| Window | Owner | Step, and why it comes here | Record to keep |
| --- | --- | --- | --- |
| 0 to 1 hour | Security lead | List every appliance of the vendor, its model family and software version. PAN-OS (CVE-2026-0322): run `show system info` and read model and sw-version, or read Dashboard > General Information; check Panorama and each firewall it manages. SonicOS (CVE-2026-19868): read the firmware version in the management interface for every firewall of a pair and every NSv. Match each version to the vendor's fixed-build table for its own release train.<br>The fixed build differs per train, so a version that looks recent can still be below its train's fix (PAN-OS 11.2.13-h2 and 11.2.15 are both affected). | One row per device: name, model, version, fixed build for its train, affected yes or no. |
| 0 to 1 hour | Security lead | Check the exposure conditions the advisory names. PAN-OS CVE-2026-0322: read Device > Setup > Interfaces > Management Interface Settings > Permitted IP Addresses, and Network > Network Profiles > Interface Mgmt for any profile that allows HTTPS or SSH on a data-plane interface. Then test from a host outside your network, such as a cloud instance, with `nmap -Pn -p 22,443 <management-address>` and `curl -sk -m 5 -o /dev/null -w "%{http_code}\n" https://<management-address>/`; any answer means the interface is reachable from the internet. SonicOS (CVE-2026-19868) has two preconditions. First, SAML is the login method for SSLVPN users: review the SSLVPN user authentication settings in the management interface. Second, at least one LDAP, RADIUS or TACACS+ server is active: open Device > Users > Settings > Authentication, then Configure RADIUS > Settings > RADIUS Servers, Configure LDAP > Settings > LDAP Servers and Configure TACACS+ > Settings > TACACS+ Servers; any server listed and not disabled counts. If either half fails, the bypass does not apply to that firewall. The attacker also needs valid credentials for one of those alternate methods, so list who holds accounts in those directories and confirm whether the SSLVPN portal answers from an untrusted network.<br>A flaw with a stated precondition is not the same urgency on every box; the answer sorts devices into reachable now and not reachable. | Per device: management address reachable from the internet yes or no, and the precondition result. |
| 0 to 4 hours | Platform engineering | Cut reachability before the patch. For PAN-OS, set Permitted IP Addresses to one jump box, which is the only system allowed to reach the management interface. For SSLVPN flaws, restrict the portal to known source ranges only if remote staff can work without it. Test from an untrusted network that the management address no longer answers.<br>This is the one action that fits inside the first hours without an outage window; the CVSS 4.0 requirement of a high-privilege account means it removes the network path an attacker needs. | The change ticket, the before and after Permitted IP Addresses, and the outside test result. |
| 0 to 4 hours | Security lead | Pull forensic evidence before any upgrade. On PAN-OS export device state (Device > Setup > Operations > Export device state) and save System, Config and Authentication logs from Monitor > Logs. Save the configuration audit and the administrator list (Device > Administrators). Send logs to storage the appliance cannot write to.<br>An upgrade restarts the device and can overwrite logs, and CISA marked forensic triage as required for the PAN-OS KEV entry. | File names, hashes and the time of export, kept with the incident record. |
| 0 to 4 hours | Security lead | Search the exported logs and the firewall traffic logs for the indicator addresses the vendor published. For CVE-2026-0322 these are 66[.]42[.]72[.]14, 208[.]83[.]239[.]114 and 149[.]248[.]47[.]234. Palo Alto published no file or log signatures, so also list every administrator login to the management interface in the exposure window and check each against a person.<br>The vendor gives only three addresses, so an empty search proves little; the administrator login list covers what the addresses miss. | Search period, queries used, hit count (zero is a result), and the admin logins that nobody could explain. |
| 4 to 24 hours | Platform engineering | Upgrade to the fixed build for the train, in a window within the day. PAN-OS (CVE-2026-0322), by release train: 12.2 to 12.2.4; 12.1 to 12.1.4-h12, 12.1.7-h8 or 12.1.10-h2; 11.2 to 11.2.4-h22, 11.2.7-h21, 11.2.10-h15, 11.2.13-h3 or 11.2.16; 11.1 to 11.1.4-h37, 11.1.6-h39, 11.1.7-h11, 11.1.10-h35, 11.1.13-h15 or 11.1.16-h3; 10.2 to 10.2.7-h38, 10.2.10-h41, 10.2.13-h26, 10.2.16-h11 or 10.2.18-h12 (each or later in its sub-train, per Palo Alto). SonicOS (CVE-2026-19868): Gen7 to 7.3.4-7013 or higher, Gen8 to 8.2.3-8015 or higher. In an HA pair, suspend the passive node, upgrade and verify it, fail over, then upgrade the other, and take a configuration backup first. On PAN-OS run `show system info` after each node and confirm sw-version equals the fixed build.<br>Pairs let you patch with no outage, and the failover test proves traffic works on the new build before the second node changes. | Per node: build before, build after, time, and the traffic test result. |
| 4 to 24 hours | Platform engineering | For devices you cannot upgrade today, keep the reachability cut in place and apply the vendor's partial coverage if it exists. PAN-OS (CVE-2026-0322): Threat IDs 510046 and 510047 (content version 9159-10287 or later) need management traffic routed through a data-plane interface with decryption and threat prevention; treat them as partial cover only. SonicOS (CVE-2026-19868): the workaround is to disable the LDAP, RADIUS and TACACS+ servers, which removes the alternate login method the bypass needs; use it only where no one needs those servers.<br>A device that stays on a vulnerable build needs a named reason and an end date, not silence. | Device, reason it was not patched, the interim control, and the date it will be patched. |
| 24 to 72 hours | Security lead | PAN-OS (CVE-2026-0322): hunt for persistence on every device that was reachable before the cut. Open Device > Config Audit and compare the running configuration with the last backup taken before the device was first reachable from an untrusted network, not the 14 Oct 2026 disclosure date, because exploitation can predate an advisory; with no such backup, use the oldest one you hold and treat each difference as unexplained until a person owns it. Open Device > Administrators and match every account and role to a person. Read Monitor > Logs > Configuration and System for administrator logins, and for changes made by accounts nobody can explain. Check Device > Certificate Management > Certificates for certificates you did not install, and Device > Server Profiles and Device > Authentication Profile for changed RADIUS, LDAP or SAML servers. Check Network > Virtual Routers and Policies for routes, NAT and rules added since that last clean backup. Because the flaw runs code as root, a device with any unexplained change is rebuilt, not cleaned. SonicOS (CVE-2026-19868): compare SSLVPN login records with the SAML provider's sign-in log: a user on the firewall with no matching SAML sign-in came in through the alternate method. SonicWall names no log event for this bypass, so export the SSLVPN login events from the firewall event log or the syslog server for the exposure window into firewall-sslvpn-users.txt (one username per line) and the SAML sign-ins for the same window from the identity provider into idp-saml-signins.txt, then run comm -23 <(sort -u firewall-sslvpn-users.txt) <(sort -u idp-saml-signins.txt). Every name it prints logged into SSLVPN without a SAML sign-in and gets an owner's explanation, or its credentials are rotated and its sessions ended.<br>Patching does not remove access gained before it, and root access lets the attacker hide changes on the box itself, so the PAN-OS audit and administrator views are where a change shows. | Diff of config against the last known good backup, with each difference explained or escalated. |
| 24 to 72 hours | Platform engineering | If any device was reachable and cannot be cleared, rotate what it holds: administrator and service passwords, LDAP and RADIUS bind credentials, VPN pre-shared keys, SAML signing and device certificates, and force all VPN sessions to end.<br>Credentials on the device are readable by anyone with root, so a patch alone leaves them exposed. | Each secret rotated, the date, and the owner who confirmed the dependent system still works. |
| 24 to 72 hours | Security lead | Rescan from outside the network for the vulnerable version banner and the management port, and confirm each device meets its fixed build. Close the temporary jump-box rule only when the owner agrees, and keep it if no one needs the management interface from elsewhere.<br>The outside view is the only check that includes devices missing from the inventory. | Scan date, devices seen, any not in the inventory, and the sign-off. |

Print this table as the checklist: write the time each step was done in the record column.

## When no fix exists yet

Some edge flaws ship with no usable workaround. Palo Alto states that no known workaround exists for CVE-2026-0322, so the only options are to shrink who can reach the interface or to filter the traffic. A jump box that is the only system allowed to reach the management interface costs you remote administration from anywhere else, and any script that manages the device from another address stops working. Palo Alto rates that case 8.5 instead of 8.6 because the attack vector becomes adjacent, so it lowers risk a little and does not remove it. Threat IDs 510046 and 510047 cost decryption load and certificate work, and Palo Alto calls their coverage limited.

Take the device offline from the internet when three things are true: the management interface or portal is reachable from untrusted networks, the vendor or CISA reports exploitation, and the only mitigation is partial. Switching off the management interface does not stop the traffic path, so for management flaws you can usually cut reachability without ending service. For a VPN portal flaw you cannot: SonicWall's workaround for CVE-2026-19868 (updated 9 Nov 2026) is to disable or delete every LDAP, RADIUS and TACACS+ server on the firewall, under Device > Users > Settings > Authentication, which stops anything signing in through them. Decide by listing what depends on those servers before you disable them.

## CVE-2026-0322 worked through, day by day

Palo Alto Networks disclosed CVE-2026-0322 on 14 Oct 2026: code injection (CWE-94) in the PAN-OS management interface, CVSS 4.0 base score 8.6 (NVD's own CVSS 3.1 rating is 7.2), exploitable by an attacker who can reach the interface and holds a high-privilege account. The vendor said very limited exploitation had been observed. The advisory and KEV give dates, not hours, so the table runs in days and is in date order. The SonicOS rows for CVE-2026-19868 are marked and fall in the same order.

| When | What happened | Source |
| --- | --- | --- |
| 14 Oct 2026 | Palo Alto publishes the advisory with fixed builds in five release trains, exploit maturity ATTACKED and three indicator addresses. It lists no workaround; the jump-box limit and Threat IDs 510046 and 510047 are partial cover only. | [source](https://security.paloaltonetworks.com/CVE-2026-0322) |
| 14 Oct 2026 | NVD publishes the record the same day. | [source](https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-0322) |
| 14 Oct 2026 | CISA adds the CVE to KEV with a due date of 17 Oct 2026. Ransomware use is listed as Unknown. | [source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0322) |
| 15 Oct 2026 | Palo Alto records an update to the advisory. | [source](https://security.paloaltonetworks.com/CVE-2026-0322) |
| 17 Oct 2026 | KEV due date, 3 days after disclosure and listing. | [source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0322) |
| 5 Nov 2026 (SonicOS CVE-2026-19868) | SonicWall releases advisory SNWLID-2026-0014, version 1.0, which fixes seven CVEs. For CVE-2026-19868 (CVSS 3.1 7.1) a user holding valid credentials for LDAP, RADIUS or TACACS+ can bypass SAML authentication on the SSLVPN, which also defeats SAML-enforced MFA. It applies only where SAML is enabled for SSLVPN logins. Fixes: Gen7 7.3.4-7013 and Gen8 8.2.3-8015 or higher. | [source](https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0014) |
| 6 Nov 2026 (SonicOS CVE-2026-19868) | NVD publishes the record. CISA adds the CVE to KEV with a due date of 20 Nov 2026, and its SSVC entry records exploitation as active and automatable as no. SonicWall says its PSIRT investigated a report indicating potential exploitation; neither it nor CISA gives a first attack date or indicators. | [source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-19868) |
| 9 Nov 2026 (SonicOS CVE-2026-19868) | SonicWall advisory version 1.1 updates the workaround: if SAML is in use and you cannot upgrade, disable or delete every active LDAP, RADIUS and TACACS+ authentication server on the firewall. | [source](https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0014) |
| 10 Nov 2026 | Siemens adds CVE-2026-0322 to advisory SSA-104023 for RUGGEDCOM APE1808 devices running PAN-OS Virtual NGFW and sends customers to Siemens support for patch information, 27 days after the Palo Alto advisory. | [source](https://cert-portal.siemens.com/productcert/html/ssa-104023.html) |

Disclosure and KEV listing came on the same day, so there was no gap in which to wait: the exposure check in hour 1 and the jump-box rule by hour 4 would have been in place before the 17 Oct due date, three days later. The fixed build depended on the train, and embedded copies such as the Siemens appliances waited 27 days for a vendor path, so the inventory in hour 1 has to include third-party devices that run PAN-OS. Because the flaw needs a high-privilege account, the administrator list review in hour 4 matters as much as the version.

## Related pages

- [Cisco ISE network access control playbook: the first 72 hours after a critical flaw](/playbooks/network-access-control/)
- [Dependency playbook: the first 72 hours when a library you ship has a critical flaw](/playbooks/dependency/)
- [Container base image playbook: the first 72 hours when a flaw is in the image your services build on](/playbooks/container-base-image/)

## Sources

- Palo Alto Networks advisory CVE-2026-0322: https://security.paloaltonetworks.com/CVE-2026-0322 (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)
- NVD record for CVE-2026-0322: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-0322 (read 19 Nov 2026)
- Siemens ProductCERT advisory SSA-104023: https://cert-portal.siemens.com/productcert/html/ssa-104023.html (read 19 Nov 2026)
- SonicWall advisory SNWLID-2026-0014 (CVE-2026-19868): https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2026-0014 (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)

Last reviewed 19 Nov 2026. Canonical: https://zerodayplaybook.com/playbooks/network-edge-appliance/
