External risk intelligence

NGINX HTTP/3 Use-After-Free Leads to Restart or Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-121810

NGINX is a primary internet-facing web server and reverse proxy, typically deployed at the network edge to handle public-facing HTTP/3 traffic. Given its standard role as a public gateway and web entry point, the vulnerable service is designed to be directly exposed to the internet.

Use After Free

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A newly disclosed security vulnerability affects NGINX configurations using HTTP/3. While exploitation is complex and depends on specific environmental conditions, it could potentially allow an unauthenticated attacker to cause a denial-of-service or, in certain circumstances, execute code. The primary concern at this time is to confirm if our NGINX deployments utilize HTTP/3 and assess our exposure.

  • Attack could crash or control NGINX servers.
  • NGINX servers often handle public web traffic.
  • Confirm HTTP/3 usage and assess impact.

Attack Path

How an attacker could exploit the issue

An attacker could target NGINX instances using HTTP/3. By sending specially crafted requests, they might trigger a use-after-free error within the NGINX worker process. This could lead to a server restart, and under certain conditions, potentially enable code execution if ASLR is not active or can be bypassed.

  • Entry: Exposed NGINX with HTTP/3.
  • Trigger: Specially crafted network requests.
  • Risk: Server restart or code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could affect NGINX Plus and NGINX Open Source configurations using HTTP/3. An attacker could trigger a use-after-free condition in the worker process, potentially leading to a service restart or, under specific conditions like disabled ASLR, code execution. This is a data plane issue, meaning control plane data is not directly exposed.

  • Data plane service availability.
  • Remote attacker triggers use-after-free.
  • Denial-of-service or code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world action likely falls to infrastructure or platform teams managing NGINX deployments. The first practical step is to inventory all NGINX instances, determine their exposure to the internet, and identify the business criticality of any services using HTTP/3. Once accountable owners are identified, a risk-based remediation plan can be developed.

  • Identify NGINX instances and HTTP/3 usage.
  • Confirm internet exposure and business criticality.
  • Plan remediation with accountable owners.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is NGINX and why is it used?

NGINX is a high-performance web server and reverse proxy used to handle incoming network traffic. It acts as a gateway for websites and applications, directing user requests to the correct internal services. NGINX Plus and NGINX Open Source are widely used to manage public web traffic, load balance requests, and provide core connectivity for modern web infrastructure.

What does this use-after-free vulnerability mean for CVE-2026-121810?

This vulnerability involves a memory management flaw known as a use-after-free, classified as CWE-416. It occurs when the software continues to use a memory location after it has been cleared or deallocated. In the context of CVE-2026-121810, this instability in the NGINX worker process can crash the service or, under specific circumstances, allow an attacker to execute unauthorized code.

How can an attacker trigger this issue?

An attacker triggers this by sending specifically crafted network requests to an NGINX server configured to use HTTP/3. Success is not guaranteed, as exploitation depends on environmental conditions beyond the attacker's direct control. Simply using NGINX without the HTTP/3 protocol enabled does not trigger this specific memory error.

Is my NGINX instance relevant to this threat?

If you are running NGINX with HTTP/3 enabled, your instance is a potential target. Halo Surface Signal notes that NGINX is frequently deployed at the network edge as a primary, internet-facing gateway. Because this is a data plane issue, any NGINX system handling public traffic is more relevant than internal-only services, though all instances using HTTP/3 should be reviewed.

What should I do first to manage this risk?

Begin by auditing your infrastructure to create an inventory of all NGINX instances. Verify which of these are currently configured to use HTTP/3 and confirm their level of exposure to the internet. Once you have identified these specific assets, determine their business criticality to help prioritize your remediation efforts and coordinate with the teams responsible for those systems.

References