External risk intelligence

NGINX HTTP/2 Use-After-Free Vulnerability Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2026-123633

NGINX is a widely used web server and reverse proxy, typically deployed at the network edge to handle incoming internet traffic. Because it is designed to be public-facing to manage client connections and proxy requests, the vulnerable HTTP/2 processing functionality is exposed to the internet by default in 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

A critical vulnerability has been identified in NGINX Plus and NGINX Open Source when configured for HTTP/2 client connections. This issue, stemming from a use-after-free condition, could allow attackers to disrupt services or, in certain configurations, execute unauthorized code. The vulnerability is located in the data plane, meaning it directly affects how traffic is processed.

  • Specially crafted requests can crash NGINX.
  • It affects widely deployed web server software.
  • Confirm NGINX relevance and exposure for your environment.

Attack Path

How an attacker could exploit the issue

An attacker can target NGINX systems processing HTTP/2 traffic by sending specially crafted requests. If the NGINX worker process is under resource pressure, this can lead to a use-after-free vulnerability, potentially enabling remote code execution, especially if ASLR protections are weakened or absent.

  • Network exposure required.
  • Crafted HTTP/2 request triggers vulnerability.
  • Denial-of-service or code execution risk.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could impact NGINX systems processing HTTP/2 client requests when running low on worker connections. Under specific conditions, attackers could potentially execute code if Address Space Layout Randomization (ASLR) is disabled or bypassed, leading to denial-of-service or code execution on the data plane.

  • Affected: NGINX system data and service behavior.
  • Exposure: Specially crafted HTTP/2 requests.
  • Consequence: Denial-of-service or code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects NGINX Plus and NGINX Open Source when configured for HTTP/2 client connections, potentially leading to denial-of-service or code execution. Initial focus should be on identifying all NGINX deployments, confirming their exposure and criticality, and then assigning ownership for remediation planning.

  • Identify and inventory all NGINX instances.
  • Verify external reachability and business criticality.
  • Plan and coordinate 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 widely used to manage internet traffic. Organizations deploy it as a gateway to handle client requests, distribute load across backend servers, and serve web content. It is a fundamental component of modern web infrastructure.

What does use-after-free mean in CVE-2026-123633?

This vulnerability is classified as CWE-416, a use-after-free error. It occurs when software continues to use a memory address after it has been cleared or freed. In this case, specially crafted HTTP/2 requests can cause NGINX to incorrectly manage memory during processing, potentially leading to a system crash or unauthorized code execution.

How is this NGINX vulnerability triggered?

An attacker triggers this by sending a specially crafted HTTP/2 request to an affected NGINX server. The condition specifically requires the server's worker process to be low on available connections. If the server is not under this specific resource pressure, the vulnerability is not triggered.

Do I need to worry if my NGINX is internal?

Halo Surface Signal indicates that because NGINX is typically deployed at the network edge to manage incoming client traffic, the vulnerable HTTP/2 processing is often exposed to the internet. If your instance is truly isolated from public access, the risk is lower, but you should still assess whether internal users or compromised adjacent systems could send the required requests.

When should I prioritize fixing this CVE?

You should prioritize this by first performing an inventory to locate all NGINX instances in your environment. Confirm which systems have HTTP/2 enabled and are reachable from untrusted networks. Once identified, coordinate with the teams responsible for those servers to plan your patching or configuration updates.

References