Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-123634: DNS resolver use-after-free in NGINX

Published Nov 18, 2026 · Updated today
Trending this week#9of 430,193 vulnerabilities
Mention activity · 30 days125 mentions · peak 85 in a dayToday
CVSS9.2Critical · v4
EPSS1.6%76th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-123634CWE-416 · Use After Free

CVE-2026-123634 is a use-after-free vulnerability in the DNS resolver of NGINX Plus and NGINX Open Source. It affects proxy configurations that use variables in proxied server names and SSI or mirror subrequests that resolve the same server name concurrently. A specially crafted HTTP request triggering this resolution behavior can corrupt worker-process memory or crash the worker. Remote code execution may also be possible if ASLR is disabled or bypassed.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An unauthenticated remote attacker can cause worker-process crashes and service disruption or corrupt worker memory. Successful code execution can compromise the confidentiality and integrity of data and resources accessible to the NGINX worker account. Execution occurs with worker-process privileges; root access or container escape requires a separate privilege-escalation vulnerability or other enabling condition.

Mitigation

If you can’t patch tonight, do this now.

Replace variable-based proxied server names and request-time DNS selection with fixed upstream targets, or remove the affected SSI and mirror subrequest paths. Disabling mirror alone is insufficient if SSI can still trigger resolution of the same name. Disabling HTTP/2 does not mitigate this vulnerability. Retain ASLR as defense in depth, but do not treat it as a substitute for patching.

Remediation

Patch, then assume compromise.

Upgrade NGINX Open Source to 1.30.7 stable, 1.31.9 mainline, or a later fixed release. Upgrade NGINX Plus 37.x to 37.0.8.1 or 37.3.0.1, as appropriate for the release track, or a later fixed release. Migrate affected releases without an available fix to a supported fixed release. Distribution-provided backports are also valid; verify the complete package revision against the applicable vendor advisory rather than relying on the upstream version banner. Update embedded deployments and container images separately. Restart NGINX or perform a supported live binary upgrade so the patched executable replaces all vulnerable workers; a configuration reload alone is insufficient.

Public exploits

Exploits

1 exploit validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-123634The nine-file repository contains a standalone Python crash-trigger client and a Docker Compose reproduction lab, not an exploit-framework module. Its three Python programs implement the request loop, a minimal HTTP backend, and a threaded delayed DNS responder. Two Dockerfiles package the supporting services; nginx configuration and an HTML page supply variable-based proxying and four SSI includes; README.md documents the claimed vulnerability and usage. poc.py defaults to 200 sequential requests against http://127.0.0.1:8080, setting X-Target: uaf.test on trigger requests. The intended race occurs within nginx's processing of SSI subrequests. The DNS service delays responses by 400 ms and resolves queries to the backend. The client counts network/HTTP failures and failed health checks, then labels any recorded failure as vulnerable. It does not inspect a crash dump, prove a use-after-free, or distinguish unrelated failures from exploitation. Health checks omit X-Target, and nginx's configured 30-second DNS cache further means that fresh overlapping resolutions on every request are not established. The supplied material claims CVE-2026-123634, affected nginx versions 0.6.18–1.31.8, and fixes in 1.30.7/1.31.9. These claims and the proposed resolver lifetime mechanism cannot be verified from this repository alone. There is no nginx source patch, sanitizer trace, captured crash, or RCE payload. No obvious operator-destructive commands or exfiltration behavior appear, so there is insufficient evidence to classify it as deliberately fake, but exploit validity remains unconfirmed. Documentation diverges from the implementation: several advertised flags do not exist, the documented request count differs, and the patch-test command references a missing nginx/Dockerfile although Compose uses an image directly. The referenced advisory and CVE websites are documentation links, not endpoints contacted by the code. Repository URL, git reference, and archive size were not supplied; their metadata fields use empty/zero placeholders. The listed file sizes total 11,583 bytes, which is not an archive-size measurement.LLCForge · Disclosed Nov 18, 2026 · python · html · network · webPoC
FAQ

Frequently asked questions

Is CVE-2026-123634 exploited in the wild?
As of Nov 19, 2026, Mallory has no reports of CVE-2026-123634 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-123634?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-123634, the earliest disclosed Nov 18, 2026.
Is there a patch for CVE-2026-123634?
Upgrade NGINX Open Source to 1.30.7 stable, 1.31.9 mainline, or a later fixed release. Upgrade NGINX Plus 37.x to 37.0.8.1 or 37.3.0.1, as appropriate for the release track, or a later fixed release.
How severe is CVE-2026-123634?
CVE-2026-123634 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 1.6% (76th percentile) as of Nov 19, 2026.
Activity feed

Recent activity

125 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
si cert blogNews · Nov 19, 2026SI-CERT 2026-09 / Kritične ranljivosti v spletnem strežniku NGINX - nginx2root - SI CERTA use-after-free vulnerability involving NGINX DNS-query and reverse-proxy request processing. The listed exploitation conditions involve resolver, dynamic proxy_pass, and mirror with mirror_request_body off. The advisory describes possible arbitrary code execution with NGINX worker-process privileges, depending on version and configuration. It belongs to the NGINX2Root group. Fixed NGINX Open Source releases are 1.30.7 and 1.31.9. Disabling HTTP/2 does not address this vulnerability.Read more ↗ncsc huNews · Nov 19, 2026Riasztás az NGINX kritikus sérülékenységeiről - Nemzeti Kiberbiztonsági IntézetAn NGINX use-after-free vulnerability in DNS resolution and subrequest handling, exploitable under particular proxy configurations. It is part of the NGINX2Root group of five critical vulnerabilities described as potentially permitting unauthenticated remote code execution with worker-process privileges. The advisory recommends patched releases and reviewing or temporarily restricting proxy configurations that use dynamic DNS resolution. Disabling HTTP/2 does not protect against this flaw.Read more ↗thecyberexpress com vulnerabilitiesNews · Nov 19, 2026NGINX Patches CVE-2026-123633 And CVE-2026-123007 RCE FlawsAn NGINX DNS resolver use-after-free vulnerability rated 9.2, fixed in the release discussed in the article.Read more ↗malware newsNews · Nov 19, 2026NGINX2Root: What NGINX Admins Should Know - Malware News - Malware Analysis, News and IndicatorsAn NGINX2Root use-after-free vulnerability in the DNS resolver, affecting upstream versions 0.6.18 through 1.31.8 when a request-derived proxy_pass target is combined with SSI or mirror subrequests. The article describes potential unauthenticated code execution with worker privileges and assigns F5's CVSS v4.0 score of 9.2. Fixed releases include NGINX Open Source 1.30.7 and 1.31.9 and NGINX Plus 37.0.8.1 and 37.3.0.1. Using a static upstream instead of a request-derived hostname is a temporary mitigation; disabling mirror alone is insufficient. No public exploit code or in-the-wild exploitation was reported as of November 19, 2026.Read more ↗
+83 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity23Community discussion across Reddit, Mastodon, and other social sources.