A memory safety flaw has been disclosed in NGINX Plus and NGINX Open Source setups that use HTTP/3. A remote attacker who does not need to log in can trigger a use-after-free condition in an NGINX worker process. This forces the worker to restart. On systems where Address Space Layout Randomization (ASLR) is turned off or can be bypassed, the attacker may also be able to execute code.
The advisory was published in the GitHub Advisory Database on 18 November 2026, together with two related NGINX use-after-free flaws. The three issues are tracked as CVE-2026-121810, CVE-2026-123634 and CVE-2026-113425. The highest CVSS score among them is 9.2. The sources do not credit individual researchers. At the time of writing, none of the flaws is listed in CISA's Known Exploited Vulnerabilities catalogue, and there are no public reports of attacks.

What is affected
The advisories do not list specific affected or fixed version numbers. They also note that versions which have reached End of Technical Support are not evaluated. Based on the descriptions, you are in scope if you run NGINX Plus or NGINX Open Source in any of these setups:
- HTTP/3 enabled: the main issue covered here.
- Reverse proxy with variables in the upstream server name, combined with Server Side Includes (SSI) or a
mirrordirective that sends a subrequest to a location resolving the same server name. - Mail proxy: NGINX configured to proxy mail traffic.
If you run an older NGINX version that is out of support, assume it may be affected, since it was not assessed.
What goes wrong
A use-after-free happens when software keeps using a piece of memory after it has already released it. Whatever now sits in that memory can be read or changed in ways the program did not expect. In the HTTP/3 case, specially shaped traffic can push the worker process into this state. The advisory says exploitation also depends on conditions outside the attacker's control, so it is not guaranteed to work every time.
In all three flaws, the likely result is a crashed worker process or corrupted memory. Code execution is possible but harder: it needs ASLR to be disabled or for the attacker to find a way around it. The vendor describes the HTTP/3 and mail proxy issues as data plane only, with no exposure of the control plane.
Why it matters
NGINX sits in front of a large share of websites and apps, including many Shopify headless builds, WordPress, Magento, Next.js, Node and PHP stacks. It often handles every request before your application sees it. A worker that keeps crashing means dropped connections and an unstable site. Repeated crashes can amount to a denial of service.
Code execution on the web server is the more serious outcome. A successful attacker could run commands on the machine that terminates your TLS traffic and talks to your back end. That is why these flaws rate as high as 9.2, even though they are not simple to exploit.
What to do now
- Find every NGINX instance you run, including load balancers, containers, Kubernetes ingress controllers and staging servers. Note the edition (Plus or Open Source) and version.
- Check your configuration for HTTP/3 (QUIC listeners), the mail proxy module, and proxy setups that use variables in the upstream address together with SSI or
mirror. - Apply the vendor's fixed release. The advisories we reviewed do not state fixed version numbers, so check the official NGINX security advisories or your Linux distribution's packages for the patched build.
- If you cannot patch straight away and do not need HTTP/3, consider turning it off until you update. Do the same for mail proxying, SSI or mirroring where they are not essential.
- Make sure ASLR is enabled on the host. It is on by default in most modern Linux distributions. Keeping it on makes code execution much harder.
- Move off unsupported NGINX versions. They were not evaluated for these flaws.
- Watch your logs for frequent worker restarts or crashes, which could signal attempts to trigger the bug.
If you use a managed host or a CDN that runs NGINX for you, ask your provider whether they have applied the fix.
Not sure if this affects you? Talk to us and we will check your sites and servers and plan the update with you.
Sources
- This issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/3.: GitHub Advisories, 19 November 2026
- This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied...: GitHub Advisories, 19 November 2026
- When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause...: GitHub Advisories, 19 November 2026
