NGINX HTTP/3 use-after-free, RCE risk

Critical 9.2 CVE-2026-121810

High risk · public exploit

Severity 9.2 Reach 10.0 Ease 3.0 Exploitation 2.0 Tooling 5.0

Risk assessment

NGINX HTTP/3 use-after-free lets unauthenticated attackers crash workers or possibly run code (CVSS 9.2). Update to the fixed NGINX release.

By Yazoul AI · automated

What to do

Apply the latest security patches from the vendor. If patching is not immediately possible, review the mitigation steps in this advisory and monitor for exploitation attempts.

Exploitation confirmed - public proof-of-concept - CVE-2026-121810 is a critical use-after-free in NGINX Plus and NGINX Open Source configurations that enable HTTP/3, and it lets a remote, unauthenticated attacker crash the worker process or potentially execute code. The vendor has shipped fixed releases; update immediately.

Overview

NGINX handles HTTP/3 in a worker process that parses and tears down QUIC connections. In affected builds, a specific sequence of HTTP/3 traffic can leave a memory structure in use after it has been freed. When the worker later touches that stale memory, the process crashes and restarts. The attacker does not need credentials or any interaction from a legitimate user.

Two qualifiers keep this from being a trivial attack. The 9.2 severity comes with a HIGH attack complexity rating: a successful trigger depends on timing and state outside the attacker’s control. The second qualifier concerns code execution. Turning the crash into reliable code execution requires that ASLR be disabled, or that the attacker has a separate way to defeat it. That combination is uncommon, but it exists on hardened and embedded deployments with weakened memory protections.

It is worth noting what this is not. The control plane is unaffected; NGINX management and API interfaces are not exposed by this bug. This is a data plane issue only, which limits blast radius but does not reduce urgency for internet-facing HTTP/3 endpoints.

Impact

For most organizations the realistic outcome is denial of service. Each crash restarts a worker, dropping in-flight requests and degrading capacity. Repeated triggering can produce a sustained outage pattern that looks like a crash loop rather than a clean attack. On systems with ASLR disabled, or where the attacker can bypass it, the same flaw could be chained into remote code execution within the worker context.

Remediation and Mitigation

  • Upgrade NGINX Plus and NGINX Open Source to the fixed release named in the vendor advisory. Note that releases past End of Technical Support are not evaluated and will not receive a fix.
  • If you cannot patch immediately, disable HTTP/3 and fall back to HTTP/2 or HTTP/1.1 on affected listeners. This removes the vulnerable parsing path entirely.
  • Do not rely on “we don’t use HTTP/3” without checking. The directive is often enabled in a shared config template and inherited by hosts that never intended it.
  • Verify ASLR is enabled (/proc/sys/kernel/randomize_va_space should read 2) on internet-facing hosts, as defense in depth.
  • Monitor worker restart counts and core dumps for unexplained process exits on HTTP/3 listeners.

For related incident context, see breach reports and security news.

Security Insight

The CVSS 9.2 score against a HIGH attack complexity vector is a useful reminder that scoring amplifies severity while a well-placed configuration change can neutralize it. This case also mirrors the recurring HTTP/3 maturity problem: QUIC stacks are younger than their HTTP/1.1 predecessors, and use-after-free bugs in connection teardown have appeared across multiple implementations. Organizations that enabled HTTP/3 early for performance gains now carry a code path their monitoring was never designed to watch.

Further Reading

Exploit references 1 PoC Show

Public PoC References

Unverified third-party code

These repositories are publicly listed on GitHub and have not been audited by Yazoul Security. They may contain malware, backdoors, destructive payloads, or operational security risks (telemetry, exfiltration). Treat them as hostile binaries. Inspect source before execution. Run only in isolated, disposable lab environments (offline VM, no credentials, no production data).

Authorized use only. This information is provided for defensive research, detection engineering, and patch validation. Using exploit code against systems you do not own or do not have explicit written permission to test is illegal in most jurisdictions and violates Yazoul's terms of use.

Repository Stars
LLCForge/CVE-2026-121810

CVE-2026-121810 — nginx HTTP/3 (QUIC) use-after-free under worker_connections exhaustion. Affects nginx 1.25.0–1.31.8. Docker PoC.

★ 0

Showing 1 of 1 known references. Source: nomi-sec/PoC-in-GitHub.

Share

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.