CVE-2026-121810·Nginx vulnerability
Description: This issue affects NGINX Plus and NGINX Open Source configurations that use HTTP/3. A remote, unauthenticated attacker can cause a use-after-free condition in the NGINX worker process, leading to a restart. Exploitation also depends on conditions beyond the attacker’s control. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
- Severity
- high
- Software
- Nginx
- Fixed in
- 1.30.7
- Published
Affected versions
From: 1.25.0
Until: 1.30.6
Fixed in: 1.30.7
How to fix this CVE
Upgrade Nginx to version 1.30.7 or later to patch a use-after-free vulnerability affecting HTTP/3 implementations. Organizations running Nginx Plus or Open Source editions with HTTP/3 enabled should prioritize this update to prevent denial-of-service conditions and potential code execution on systems without ASLR protections. Apply the patch across all affected instances and validate HTTP/3 connectivity after the upgrade. Hosted Power publishes patched nginx packages that carry the complete nginx2root fixes for Debian 8 Jessie through 13 Trixie, CentOS 7 (archived EPEL) and CentOS 8 AppStream (streams 1.14, 1.16, 1.18 and 1.20), under the MIT licence: https://github.com/HOSTED-POWER/nginx2root-patches. These are not a mitigation and need no follow-up: each package is that release's own nginx source with every nginx2root patch that applies to it, so nothing further is required. For Debian 8 to 11 and CentOS 7 and 8 no official update is coming at all, which makes them the fix rather than a stand-in. On Debian 12 and 13, where an official update may still ship, the package version deliberately sorts below Debian's expected one (for example 1.22.1-9+deb12u10.1~hp1 on Bookworm) so apt takes over cleanly when it arrives, with no pinning. Patches, checksums, tests and reproducible build instructions are public; we checked the repository on 19 November 2026 (v1.3.2). Note that disabling HTTP/2 does not address the resolver and mail proxy issues in this set. Enterprise Linux is covered too, as of 19 November 2026: RHEL 8 and Rocky Linux 8 (the nginx:1.24 module stream); RHEL 9, Rocky Linux 9 and Oracle Linux 9 across the base 1.20 stream and AppStream 1.22, 1.24 and 1.26; AlmaLinux 9's retired 1.22 stream; and RHEL, Rocky Linux and Oracle Linux 10. On the 10 releases the situation differs by vendor and it matters: AlmaLinux 10 has shipped an official fix, while RHEL 10 and Rocky Linux 10 have not — both still ship nginx 1.26.3-16.el10_3.1, which predates the disclosure. Do not assume a current EL 10 system is patched because a sibling distribution is.
sudo dnf update nginxDefensia detects this vulnerability
How to check if you are affected
- Check installed Nginx version: nginx -v
- Verify if HTTP/3 (QUIC) is enabled in nginx.conf: grep -r 'listen.*quic' /etc/nginx/ || grep -r 'http3' /etc/nginx/
- Review Nginx error logs for segmentation faults or worker process crashes: tail -100 /var/log/nginx/error.log | grep -i 'segmentation\|worker.*exited\|use-after-free'
- Confirm patch application by running: nginx -v and verifying the version matches 1.30.7 or higher
- Step 5: If your distribution backported the fix, the version number will not show it. Debian, Ubuntu and the RHEL family ship security fixes inside the existing upstream release — Ubuntu's nginx 1.24.0-2ubuntu7.20 carries this fix and still answers "nginx/1.24.0" — so every version check above, and every external scanner, will keep calling a patched host vulnerable. Read the changelog of the package that is actually installed, which names the CVE: `zgrep -i CVE-2026-121810 /usr/share/doc/nginx*/changelog.Debian.gz` on Debian and Ubuntu, or `rpm -q --changelog nginx | grep -i CVE-2026-121810` on RHEL, Rocky, AlmaLinux and Oracle Linux. Use the file on disk rather than `apt changelog`: that command reads repository metadata, so it describes what the repository holds rather than what you are running, and it does not reliably show third-party packages — including backported ones. A match means this build carries the fix. The reverse does not hold: a CVE absent from the changelog may simply never have applied to that build, so absence is not confirmation that you are exposed.
FAQ
What is CVE-2026-121810?
This vulnerability is a use-after-free condition in Nginx's HTTP/3 implementation that allows unauthenticated remote attackers to crash worker processes or potentially execute arbitrary code when ASLR is disabled.
Is CVE-2026-121810 being actively exploited?
No, according to CISA's Known Exploited Vulnerabilities (KEV) catalog, this vulnerability is not currently being exploited in the wild, and no public exploits are available.
What versions of Nginx are affected by CVE-2026-121810?
Nginx versions prior to 1.30.7 are affected when HTTP/3 is configured; both Nginx Open Source and Nginx Plus are vulnerable.
How do I check if my server is vulnerable to CVE-2026-121810?
Run 'nginx -v' to confirm your version, then check if HTTP/3 is enabled with 'grep -r listen.*quic /etc/nginx/'; vulnerability exists only if version is below 1.30.7 AND HTTP/3 is active.
Does Defensia detect CVE-2026-121810?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Nginx is installed on a monitored server, CVE-2026-121810 will appear in your dashboard with remediation steps.
Related Nginx CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-121810. Free for 1 server.
Get started free