Organisations should patch affected NGINX deployments promptly, while separating configuration-dependent exposure from the broader update. Check live protocol and mail-proxy settings, then track embedded NGINX in Cisco and Palo Alto Networks products through the relevant vendor advisories.
That distinction matters because it tells teams where to look first. NGINX’s 18 November update fixes a broader set of flaws, including two HTTP/2 memory-safety issues—flaws in how software manages memory—that Palo Alto Networks says can let an unauthenticated attacker crash a worker process or execute arbitrary code when HTTP/2 is enabled. Cisco is tracking all five CVEs across parts of its portfolio. It says proof-of-concept code is available, but it is not aware of malicious use.
What happened
NGINX published 1.31.9 on its mainline branch and 1.30.7 on its stable branch on 18 November 2026. Both releases fix CVE-2026-113425, CVE-2026-121810, CVE-2026-123007, CVE-2026-123633 and CVE-2026-123634, alongside several other security defects. NGINX’s advisory records 1.31.9 or later and 1.30.7 or later as the fixed release floor for the five CVEs.
CVE-2026-113425 is a use-after-free defect—a flaw caused by accessing memory after it has been released—in ngx_mail_proxy_module. F5 says NGINX Open Source or NGINX Plus must be configured as a mail proxy server for the flaw to matter. A crafted mail session can crash or corrupt a worker process and may permit code execution where address-space layout randomisation (ASLR), a memory-protection technique, is disabled or can be bypassed. It affects versions 0.5.33 through 1.31.8.
CVE-2026-121810 is a use-after-free in the HTTP/3 module, affecting versions 1.25.0 through 1.31.8. HTTP/3 runs over QUIC rather than TCP (Transmission Control Protocol). An HTTPS virtual host using HTTP/2 is not therefore automatically exposed. Establish whether the HTTP/3 module is built and whether QUIC/HTTP/3 is enabled at the edge before treating a service as exposed.
The serious HTTP/2 defects in the same release are different CVEs: CVE-2026-123007, a memory-corruption issue in HTTP/2 flow control, and CVE-2026-123633, a use-after-free in HTTP/2. Those are the flaws Palo Alto Networks has assessed for PAN-OS and Panorama. Treating all five identifiers as interchangeable creates false positives and can leave the actual HTTP/2 exposure without a clear owner.
Timeline and confirmed vendor position
NGINX released the fixed Open Source versions on 18 November 2026. Cisco published its portfolio advisory on 20 November 2026, describing its work as an ongoing investigation and promising updates as product assessments complete. As of the advisory’s current version, Cisco identifies the following status:
- Identity Services Engine (ISE): only Release 3.5 is affected; Cisco lists 3.5 Patch 5, expected in December 2026, as the first fixed release.
- NX-OS: affected, but Cisco has not yet published a first fixed release in the advisory table.
- Smart PHY: affected; 27.1.0 is forecast for March 2027.
- Intersight Virtual Appliance: 1.1.9-0 is listed as the first fixed release, expected in December 2026.
- Cisco Vulnerability Management: affected; 1.30.7 is listed as the fixed version.
Cisco also lists Catalyst Center, Catalyst SD-WAN Controller and Manager, Nexus Dashboard, ASA, FMC and FTD as not affected. Catalyst SD-WAN Validator, IOS XE, IOS XR, UCS Director and several other products remain under investigation. A product absent from the table is not cleared: Cisco explicitly says the advisory will change as assessment continues.
Palo Alto Networks’ advisory is more settled, but its scope is narrower than the NGINX headline suggests. It covers CVE-2026-123007 and CVE-2026-123633, not CVE-2026-113425 or CVE-2026-121810. Only PAN-OS and Panorama systems with HTTP/2 manually enabled are affected. The feature is a management-plane network protocol option on PAN-OS 11.2.8 and later, while HTTP/1.1 is the default. Prisma Access and other software-as-a-service (SaaS) offerings are listed as requiring no customer action because Palo Alto Networks is managing the backend rollout.
One NGINX update, several exposure conditions
“NGINX vulnerability” isn’t a useful enough asset category here. The affected code spans mail proxying, HTTP/3, HTTP/2 and DNS resolver handling. Cisco summarises the batch as affecting NGINX releases 1.9.5 through 1.31.8, so the search should be broad. That range does not mean every component is reachable or equally exposed.
For the two CVEs at the centre of this analysis, ask two direct questions: does the host use NGINX as a mail proxy, and is HTTP/3 enabled? For Palo Alto systems, establish whether HTTP/2 has been enabled on PAN-OS or Panorama. Then patch the wider batch wherever the installed version requires it.
Operational priority: patch externally reachable NGINX services and security-management interfaces first, but don’t let the word “critical” replace exposure validation. A public HTTPS endpoint with neither mail proxying nor HTTP/3 enabled may not be exposed to CVE-2026-113425 or CVE-2026-121810. It can still need the update for other flaws fixed in the same release.
Detection and response
For standalone NGINX, inventory package, container-image and source-build versions, then verify compiled modules and the live configuration. Configuration-management records help, but they often miss bundled reverse proxies, appliance services and images built months ago. Check public ingress, API gateways, mail front ends, Kubernetes edge components and administration portals before internal-only workloads.
Upgrade NGINX Open Source to 1.31.9 or later on the mainline branch, or 1.30.7 or later on the stable branch. NGINX Plus customers should use the fixed supported release F5 identifies for their entitlement and deployment. An Open Source engine number alone does not prove that an appliance or packaged product is remediated.
For PAN-OS and Panorama, Palo Alto Networks advises upgrades to PAN-OS 12.2.4-h3, 12.1.10-h6 or 11.2.16-h3, or later applicable releases. Its advisory also identifies later fixed maintenance releases for older supported trains. If an emergency upgrade is not viable, disable HTTP/2 and return to HTTP/1.1; Palo Alto documents this as a command-line interface (CLI) change. That mitigation applies to CVE-2026-123007 and CVE-2026-123633, not the mail-proxy or HTTP/3 CVEs.
Review NGINX error logs, service-monitoring data and network telemetry for unexpected worker restarts, malformed protocol traffic and unusual request failures around externally exposed services. Those are triage signals, not proof of compromise. Cisco says it knows of public proof-of-concept code but no malicious use; Palo Alto Networks likewise says it is not aware of malicious exploitation of its HTTP/2-tracked issues. Possible remote code execution is not confirmed in-the-wild exploitation.
The management plane deserves particular attention because the consequences are disproportionate. Active attacks against exposed PAN-OS management interfaces showed why a security appliance is not low-risk simply because it is a security appliance. Restrict administrative exposure while patching rather than treating the appliance’s role as a compensating control.
What organisations should change
This is a component-ownership problem as much as a patching problem. Product teams need to know not just that they run NGINX, but whether they use its mail, HTTP/2, HTTP/3, resolver and stream features. Infrastructure teams need the same answers for embedded copies in network and management products. A software bill of materials, an inventory of software components, helps only when it is matched to live configuration and internet-exposure data.
For Cisco estates, create an exception register for products whose fixes are scheduled for December 2026 or, for Smart PHY, March 2027. Record the affected CVEs, exposure path, compensating controls, vendor target date and an owner who will re-check the advisory. “Under investigation” should create a tracked review, not vanish into a monthly patch report. Cisco’s separate Nexus 9000 RCE advisory is a reminder that network operating system patching needs its own change planning rather than being handled like an ordinary Linux package update.
The practical judgement: deploy the NGINX update promptly across the affected version range, but state the exposure conditions accurately. CVE-2026-113425 is a mail-proxy problem. CVE-2026-121810 is an HTTP/3 problem. Palo Alto’s confirmed issue is HTTP/2 under a manually enabled setting. That isn’t pedantry; it is how teams patch the right systems first without overstating what has happened.
Sources and further reading
- NGINX security advisories
- NGINX release news for 1.30.7 and 1.31.9
- F5 advisory for CVE-2026-113425
- Cisco advisory: Vulnerabilities in nginx Affecting Cisco Products: November 2026
- Palo Alto Networks advisory for CVE-2026-123633 and CVE-2026-123007
- Palo Alto Networks documentation: Manage HTTP/2 Network Support
Spot an error?
If something factual looks wrong, outdated or misleading, flag it here. Corrections are reviewed separately from normal article comments and reader questions.