Telemetry clues for a CVE-2026-123634 investigation

There is no confirmed in-the-wild exploitation of CVE-2026-123634 in the reviewed sources, so telemetry cannot be reduced to a signature for a known campaign. Investigators need signals that map to the resolver, memory corruption, DNS requirements, and worker execution path. Each signal has benign explanations and needs correlation.

Vulnerability overview

CVE-2026-123634 is an NGINX resolver use-after-free affecting Open Source versions 0.6.18 through 1.31.8. The fix is in 1.31.9 and 1.30.7. The CVE is classified as CWE-416 and scored 9.2 under CVSS v4.0.

The vulnerability can terminate a worker during a failed exploit attempt. A successful attempt can turn the resolver callback path into worker-level code execution. The public research describes a tested proof and does not report a live intrusion.

Mechanism and exploitation conditions

Nginx launches resolver work when proxy_pass refers to a request-derived name that needs DNS. A mirror subrequest can create a second context for the same name. When DNS processing returns, the main request can fail to send its 502 response because the client reset the connection. Request cleanup then frees the mirror context while the resolver loop still holds a pointer to it.

The attacker needs control over the DNS answer path, such as an authoritative DNS server that nginx's resolver reaches. The HTTP request must reach a vulnerable route and create the required cleanup sequence. The final impact depends on memory reclamation and callback control. This is more specific than a generic malformed-request attempt, and logs may not retain the fields needed to prove or exclude it.

Impact

A failed attempt may appear as a crash, a burst of failed upstream requests, or resolver errors. A successful attempt may produce no obvious alert if the worker remains running long enough to execute commands. The strongest host signal is a child process launched by the nginx worker account, based on Xint's detection guidance. That event needs investigation even though unrelated scripts can run under the same account in some environments.

Affected products and scope

The version range is 0.6.18 through 1.31.8 before the fixed releases. The investigation scope also depends on configuration and network reachability. Check servers with resolver directives, variable proxy destinations, and mirror or SSI subrequests first, then extend to all systems that run an unpatched package because an inventory may be incomplete.

Distribution backports can make a vulnerable-looking version fixed, and a missing package from a vendor table is not proof of safety. Verify the full package version and the vendor advisory. Include container images and infrastructure-as-code definitions in the review.

Exposure context

ZoomEye Search app="NGINX" returned 316,220,816 product fingerprints. Filter vul.cve="CVE-2026-123634" returned 0. The product count is not evidence that an individual endpoint used the vulnerable resolver path or that it was attacked. Exposure work should be joined with DNS egress records and configuration inventories.

Remediation and mitigations

Patch to 1.31.9, 1.30.7, or a later maintained release. For temporary containment, use fixed upstream groups instead of request-time DNS lookup and remove unnecessary mirroring. Validate the configuration and worker replacement. Preserve logs before restarting or rebuilding a potentially compromised host.

Practical review items include unexpected nginx worker exits, signal 11 or segfault messages, bursts of 502 responses, resolver errors, and new child processes under the worker account. Correlate these with DNS queries to unusual domains, client resets, and the relevant nginx routes. An empty log search cannot prove that no exploitation occurred because ordinary access logs may omit resolver context and connection-level detail.

References