CVE-2026-123634: DNS resolver use-after-free in NGINX
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.
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.
Exploits
1 exploit validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit.
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.
Recent activity
125 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.