HTTP/2 is the first check here. Palo Alto Networks has published PAN-OS and Panorama guidance for two nginx flaws that can crash workers or allow unauthenticated code execution.

What is new
New vendor remediation cluster: CVE-2026-123633 and CVE-2026-123007. The official JSON publication time is November 21, 2026 at 00:15 UTC, which is November 20 at 7:15 p.m. Eastern. The page shows Published November 21, Updated November 20, and a November 20 initial-publication timeline. Those inconsistent display dates do not establish a later revision.
Palo Alto Networks rates this Critical, CVSS 4.0 base 9.2, with vendor suggested urgency Moderate. My suggested MSP priority is High when an affected build and reachable HTTP/2 processing path are confirmed. No customer deployment or exposure is assumed.
Applicability and fixes
The vendor says exposure requires the HTTP/2 option enabled on PAN-OS or Panorama. Its FAQ explicitly includes Panorama virtual and M-Series appliances, but supplies no separate Panorama version matrix. CVE-2026-123633 concerns HTTP/2 upstream proxy use-after-free when connection slots run low; CVE-2026-123007 concerns HTTP/2 flow-control integer underflow and heap overflow. Package presence alone does not establish exposure.
Use the following vendor solution-table groups to select a supported branch target. The -h* group labels include the fixed hotfix; they are not statements that every hotfix in that group remains vulnerable. Targets marked ETA are planned for November 23, 2026, rather than verified available downloads. Other listed targets have no ETA marker; binary availability and compatibility were not independently tested.
| Product branch | Vendor solution-table group | Suggested fixed target |
|---|---|---|
| PAN-OS 12.2 | 12.2.0 through 12.2.4-h* | 12.2.4-h3 or later |
| PAN-OS 12.1 | 12.1.8 through 12.1.10-h* | 12.1.10-h6 or later |
| PAN-OS 12.1 | 12.1.5 through 12.1.7-h* | 12.1.7-h15 (ETA Nov 23), or 12.1.10-h6 or later |
| PAN-OS 11.2 | 11.2.15 through 11.2.16-h* | 11.2.16-h3 or later |
| PAN-OS 11.2 | 11.2.11 through 11.2.13-h* | 11.2.13-h6 (ETA Nov 23), or 11.2.16-h3 or later |
| PAN-OS 11.2 | 11.2.8 through 11.2.10-h* | 11.2.10-h19 (ETA Nov 23), or 11.2.16-h3 or later |
The vendor says no action is needed for PAN-OS 12.1.2 through 12.1.4-h*, or 11.2.0 through 11.2.7-h*, for this advisory. Its top-level status table starts affected 12.1 at 12.1.5 and 11.2 at 11.2.8. Do not use the narrower autogenerated CPE bounds as complete affected ranges: for example, CPE applicability starts 12.2 at 12.2.4 while the solution table starts at 12.2.0, and the CPE list includes versions described elsewhere as unaffected. Confirm ambiguous or omitted builds with the vendor.
For SaaS products, the advisory says Palo Alto Networks manages backend rollout and no customer action is required. That statement does not verify completion for a named tenant. Its broad assessment-complete language also sits beside future hotfix ETAs; do not interpret it as every customer system already patched.
Exploitation and interim control
Palo Alto Networks says it is not aware of malicious exploitation. Neither CVE appears in the full CISA KEV catalog checked November 20 Eastern; there is no KEV federal remediation deadline for either in this check. No new vendor-directed compromise investigation or blanket credential rotation is specified.
The vendor workaround is to disable the HTTP/2 option on PAN-OS and Panorama, following the linked documentation and a tested change plan. Verify the control actually applies to the relevant processing path and check application impact. Restricting unnecessary reachability is an additional suggested containment measure, not a vendor-certified substitute.
MSP action sequence
Inventory: identify actual firewall and Panorama models, full builds, HTTP/2 configuration and untrusted input paths across customer environments. Contain: where applicable, disable HTTP/2 using vendor guidance while validating dependent traffic. Remediate: pilot the matched supported hotfix or later compatible release; verify download availability, especially the November 23 ETA branches. Verify: confirm the running build or effective workaround on every relevant node, then test management, HA, policy deployment and application traffic. Patching alone does not establish absence of prior compromise.
Official sources
Palo Alto Networks advisory and solution matrix · Vendor JSON · Vendor CSAF · HTTP/2 configuration documentation · Official CISA KEV data.
Last verified: November 20, 2026, Eastern. The public advisory and official JSON were accessible directly; the search retrieval service could not open the detail page. Other monitoring gaps remain separate from this finding.