everythingsfine.io

runbook / 007 · Tailwind Resource Group · Customer advisory · Disclosed November 20, 2026

Find and remove PAN-OS and Panorama exposure to the NGINX HTTP/2 flaws CVE-2026-123633 and CVE-2026-123007

F5 disclosed two critical flaws in the NGINX HTTP/2 module on November 18, 2026. Palo Alto Networks says PAN-OS and Panorama 12.2, 12.1 and 11.2 are affected only when the HTTP/2 option is enabled. Fixed releases are available for each branch. This page tells you how to find your exposure and remove it.

Applies to
PAN-OS and Panorama 12.2, 12.1, 11.2
Fix
12.2.4-h3, 12.1.10-h6, 11.2.16-h3
Severity
CVSS v4.0 9.2, urgency Moderate (Palo Alto Networks)
Exploitation
None known (Palo Alto Networks)
  1. Summary

    On November 18, 2026, F5 disclosed two flaws in the NGINX HTTP/2 module. CVE-2026-123633 is a use-after-free. CVE-2026-123007 is an integer underflow in HTTP/2 flow control. F5 says each flaw can crash an NGINX worker process, and can let a remote attacker execute code if the attacker can bypass ASLR.

    PAN-OS and Panorama contain NGINX. On November 20, 2026, Palo Alto Networks published the portfolio status advisory CVE-2026-123633. Palo Alto Networks says that:

    • The issue affects only customers who enable the HTTP/2 option on PAN-OS and Panorama.
    • PAN-OS 12.2, 12.1 and 11.2 have affected releases. The version table gives the ranges.
    • Panorama is affected, on virtual appliances and on M-Series.
    • It reviewed each on-premise product that the advisory does not list, and found it unaffected.
    • It manages the fix for its SaaS products. You have no action for them.
    • It knows of no malicious exploitation.
    • The CVSS v4.0 score is 9.2, Critical, and the suggested urgency is Moderate. Attack complexity is High.

    Upgrade PAN-OS and Panorama to a fixed release for your branch. Until you upgrade, disable the HTTP/2 option.

  2. Does this apply to you?

    You have more exposure if one or more of these statements is true:

    • Your firewall or Panorama runs an affected release in the version table.
    • The HTTP/2 option is enabled on that firewall or Panorama.
    • You run NGINX yourself, with HTTP/2 enabled, on a release before the F5 fixes. Runbook 006 covers that case.

    Palo Alto Networks says PAN-OS and Panorama without the HTTP/2 option enabled are not affected. These releases are also not affected: PAN-OS 12.1.2 to 12.1.4 and PAN-OS 11.2.0 to 11.2.7, with any hotfix. PAN-OS 11.1 and 10.2 are not in the advisory. Our reading: they are not affected. Palo Alto Networks SaaS products need no action from you.

    PAN-OS releases

    This table is from the Palo Alto Networks advisory. Panorama runs PAN-OS, so the same releases apply to Panorama. "ETA 11/23" is the date Palo Alto Networks gives for a fix that is not yet available.

    Your release Upgrade to
    12.2.0 to 12.2.4-h2 12.2.4-h3 or later
    12.1.8 to 12.1.10-h5 12.1.10-h6 or later
    12.1.5 to 12.1.7-h14 12.1.7-h15 (ETA 11/23), or 12.1.10-h6 or later
    12.1.2 to 12.1.4, any hotfix No action needed
    11.2.15 to 11.2.16-h2 11.2.16-h3 or later
    11.2.11 to 11.2.13-h5 11.2.13-h6 (ETA 11/23), or 11.2.16-h3 or later
    11.2.8 to 11.2.10-h18 11.2.10-h19 (ETA 11/23), or 11.2.16-h3 or later
    11.2.0 to 11.2.7, any hotfix No action needed

    Some hotfixes are not available yet. Palo Alto Networks gives November 23, 2026 as the ETA for 12.1.7-h15, 11.2.13-h6 and 11.2.10-h19. If you cannot wait, upgrade to 12.1.10-h6 or 11.2.16-h3, which are available now.

    NGINX that you run yourself

    A PAN-OS upgrade does not change the NGINX servers that you run yourself. For them, install NGINX Open Source 1.30.7 or 1.31.9, or NGINX Plus 37.0.8.1 or 37.3.0.1. Runbook 006 gives the affected releases, a check script that finds both flaws in your configuration, and the interim step: turn off HTTP/2.

    1. Find your release. Run the version check on each firewall and on Panorama. Compare the result with the PAN-OS releases table.
    2. Find out if the HTTP/2 option is enabled. Use request http http2 show. If it is not enabled, Palo Alto Networks says you are not affected.
    3. Disable the HTTP/2 option on affected releases. This is the Palo Alto Networks workaround. Use request http http2 disable, and keep HTTP/2 disabled until you upgrade.
    4. Schedule the upgrade. Upgrade Panorama first, then the firewalls. If your hotfix has an ETA, upgrade to the next fixed release that is available now, or wait for the ETA with HTTP/2 disabled.
    5. Check the NGINX servers that you run yourself. These servers need the F5 fixes. A PAN-OS upgrade does not change them. Use the check script in runbook 006.
    6. Look at the Palo Alto Networks advisory again before each change window. The ETAs and the version table can change.
  3. Check your PAN-OS release

    This check shows the PAN-OS release. Run it in the CLI of each firewall and of Panorama.

    Version check

    text
    show system info | match sw-version

    Compare the result with the PAN-OS releases table.

  4. Check and disable the HTTP/2 option

    Palo Alto Networks says only customers who enable the HTTP/2 option are affected. The workaround is to disable that option on PAN-OS and Panorama. The advisory links the Palo Alto Networks page "Manage HTTP/2 Network Support". That page says:

    • The option is HTTP/2 support on the firewall management plane, in PAN-OS 11.2.8 and later.
    • HTTP/1.1 is the default. HTTP/2 is enabled only if an administrator enabled it.
    • You can change the option only in the CLI. The web interface has no setting for it.
    • When HTTP/2 is enabled, HTTP/1.1 is disabled, with no fallback.

    Show the HTTP/2 option

    Run this command in the CLI of each firewall and of Panorama. It shows if HTTP/2 is enabled.

    text
    request http http2 show

    The PAN-OS CLI Quick Start lists this command in the PAN-OS 12.2 command hierarchy. It does not list it for 11.2 or 12.1, and it does not show the output. We did not run the command.

    Disable HTTP/2

    Run this command in the CLI of each affected firewall and of Panorama. It disables HTTP/2 and enables HTTP/1.1 again.

    text
    request http http2 disable

    Palo Alto Networks documents this command for the firewall. The advisory gives the same workaround for Panorama.

    Do not enable the HTTP/2 option on an affected release. If a change plan enables it, move that change after the upgrade.

  5. What to monitor

    • The Palo Alto Networks advisory. Watch for the hotfixes with an ETA, for new rows in the version table and for a change to the exploitation status.
    • Unexpected restarts of web services. F5 says CVE-2026-123007 usually ends in a segmentation fault of the NGINX worker process. We have asked Palo Alto Networks which PAN-OS process serves HTTP/2, and which system log entries show that it crashed. We will add them to this page when Palo Alto Networks answers.
    • Long HTTP/2 connections that send much data. Wiz suggests detection rules for this pattern. Rapid7 says its CVE-2026-123007 attack needs approximately 128 GB of HTTP/2 data.
    • Public exploit code. Rapid7 and Sophos report public proof-of-concept code for CVE-2026-123007. We did not examine it.
  6. References

  7. About this advisory

    This page gives the results of our analysis. It is not a statement from Palo Alto Networks or F5. Palo Alto Networks has confirmed the affected and fixed releases, the HTTP/2 condition, the workaround, the Panorama impact, the SaaS status and that it knows of no malicious exploitation. Palo Alto Networks has not stated the status of PAN-OS 11.1 and 10.2: our reading is that they are not affected. The code is licensed under the Apache License 2.0 and is supplied as it is, with no warranty. You are responsible for tests in your environment. We will update this page when the hotfixes with an ETA are available, when Palo Alto Networks changes its advisory, and when Palo Alto Networks tells us which system log entries show a crash.