CVE-2026-113425: Use-after-free in NGINX mail proxy authentication
CVE-2026-113425 is a use-after-free vulnerability in ngx_mail_proxy_module in NGINX Plus and NGINX Open Source. When NGINX operates as a mail proxy with both proxy on and auth_http configured, specially crafted mail sessions can trigger a use-after-free in a worker process. This can cause worker termination, memory corruption, or potentially remote code execution if Address Space Layout Randomization (ASLR) is disabled or bypassed. The listed upstream affected range begins at 0.5.33 and extends through 1.31.8, excluding fixed branch releases and vendor-backported fixes. The vulnerability affects the data plane only; there is no control-plane exposure.
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.
A remote unauthenticated attacker can crash an NGINX worker process or corrupt its memory, disrupting mail-proxy service and active connections. Successful code execution runs with the privileges of the affected worker process, potentially compromising data, credentials, and backend resources accessible to that process. Root access and container escape are not inherent consequences and would require additional vulnerabilities or privileges.
Mitigation
If you can’t patch tonight, do this now.
Until patched, restrict IMAP, POP3, and SMTP mail-proxy listeners to trusted networks, or temporarily disable unnecessary mail-proxy functionality. Retain ASLR and other process-hardening protections, but do not treat them as a complete mitigation because code execution remains possible if ASLR is bypassed. Monitor unexpected worker termination, core dumps, worker-launched programs, and anomalous outbound connections. Restrict worker privileges and network access to reduce post-compromise reach. Disabling HTTP/2 does not mitigate this vulnerability.
Remediation
Patch, then assume compromise.
Upgrade NGINX Open Source to 1.30.7 stable, 1.31.9 mainline, or a later fixed release in the applicable branch. For NGINX Plus, install 37.0.8.1 or 37.3.0.1, or a later fixed release in the corresponding branch. NGINX Plus R33–R36 have no listed fix and require migration to a fixed release. Distribution-managed installations may instead install vendor packages containing backported fixes; assess the complete package revision against the applicable security advisory rather than relying solely on the upstream version. Update affected container images and bundled deployments separately. Fully restart NGINX after upgrading; a configuration reload alone does not replace the running executable.
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-113425 exploited in the wild?
- As of Nov 19, 2026, Mallory has no reports of CVE-2026-113425 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-113425?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-113425, the earliest disclosed Nov 18, 2026.
- Is there a patch for CVE-2026-113425?
- Upgrade NGINX Open Source to 1.30.7 stable, 1.31.9 mainline, or a later fixed release in the applicable branch. For NGINX Plus, install 37.0.8.1 or 37.3.0.1, or a later fixed release in the corresponding branch.
- How severe is CVE-2026-113425?
- CVE-2026-113425 has a CVSS v4 score of 9.2 (Critical) as of Nov 19, 2026.
Recent activity
121 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.