External risk intelligence

NGINX Proxy Use-After-Free Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-123634

NGINX is a primary internet-facing web server, reverse proxy, and load balancer. Because the vulnerability exists in its proxy and request-handling functionality when configured to process HTTP requests, it is by design a public-facing service in most common deployments.

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

This advisory describes a critical vulnerability in NGINX, affecting how it handles certain proxied server names and directives. If exploited, this could lead to memory corruption or code execution, potentially disrupting services or compromising systems. The primary concern is to confirm if our NGINX configurations are susceptible and to what extent.

  • Improper handling of proxied server names.
  • Potential for service disruption or code execution.
  • Confirm NGINX relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could initiate an attack by sending a specially crafted HTTP request to an NGINX instance configured as a proxy. This request would target a server name that includes variables and is processed by a location that resolves the same server name via Server Side Includes or a mirror directive. This interaction could trigger a use-after-free condition, potentially leading to memory corruption or remote code execution if certain security measures like ASLR are not effectively in place.

  • Network access to NGINX proxy is required.
  • A specific HTTP request triggers the vulnerability.
  • Risk includes memory corruption or code execution.

Live Threat

Current exploitation, exposure, and threat context

When NGINX is configured as a proxy and handles specific server name variables, a specially crafted request could trigger a use-after-free condition. This may allow an attacker to crash the NGINX worker process, corrupt memory, or, under certain conditions like disabled ASLR, execute code.

  • Worker process memory and availability.
  • Specially crafted HTTP requests.
  • Potential remote code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world action for this vulnerability likely involves NGINX administrators, platform teams, or application owners responsible for the web infrastructure. The first critical step is to determine the scope of exposure by identifying all NGINX instances, assessing their network reachability and business criticality, and locating the accountable system owner. Remediation planning should then be risk-driven, considering factors like potential for code execution and the availability of maintenance windows.

  • Identify NGINX instances and owners.
  • Verify critical and exposed deployments.
  • Plan remediation based on risk.

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 widely deployed web server that functions as a reverse proxy, load balancer, and HTTP cache. Developers use it to manage traffic for web applications, sitting between users and backend servers to route requests, improve performance, and handle SSL/TLS termination. Because it acts as a gatekeeper, it is frequently placed at the edge of network infrastructure to handle incoming client connections.

What does CWE-416 mean in the context of CVE-2026-123634?

CWE-416 identifies a use-after-free weakness. This occurs when a program continues to use a pointer to a memory location after that memory has been freed or cleared. In this CVE, specific complex proxy configurations cause NGINX to incorrectly manage memory during subrequests. This glitch can leave the program's memory state unstable, potentially allowing an attacker to manipulate it to crash the service or run unauthorized commands.

How can an attacker trigger this NGINX vulnerability?

An attacker triggers this by sending a specially crafted HTTP request to an NGINX proxy that uses specific variable-based server names. The vulnerability requires the proxy to execute a Server Side Include or mirror directive that targets the same server name. If these exact configuration conditions are not met, the memory error will not occur, meaning standard, simple reverse proxy setups without these specific directives remain unaffected.

Why does Halo Surface Signal categorize this as external?

Halo Surface Signal identifies NGINX as a primary, internet-facing component by design. Because this vulnerability is triggered via HTTP requests over the network, any instance of NGINX configured as a proxy and reachable from the internet is considered exposed. If your NGINX instance faces the public web, it is inherently more reachable by potential attackers, making this flaw a high priority for review.

What should I do first to manage this CVE?

Start by identifying every NGINX instance in your environment and verifying its current configuration. Focus on those acting as proxies that utilize variable-based server names or SSI/mirror directives, as these are the necessary components for the flaw. Once you have a list of active proxies, confirm which are internet-facing to prioritize your review, and coordinate with your infrastructure team to plan updates or configuration changes.

References