Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-113425: Use-after-free in NGINX mail proxy authentication

Published Nov 18, 2026 · Updated today
Trending this week#11of 430,159 vulnerabilities
Mention activity · 30 days121 mentions · peak 86 in a dayToday
CVSS9.2Critical · v4
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
IdentifiersCVE-2026-113425CWE-416 · Use After Free

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.

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.

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.

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-113425The repository contains nine files: three Python programs, three Dockerfiles, Docker Compose configuration, nginx configuration, and a README. The standalone entry point, poc.py, sends IMAP traffic and forces TCP resets using SO_LINGER=(1,0). Its four modes reset after the greeting, immediately after LOGIN, after a successful-login response, or across concurrent mixed-timing connections. Burst mode defaults to 20 connections and caps simultaneous workers at 64. It does not inspect nginx logs, process IDs, or target health to establish exploitation. The supporting lab uses nginx:1.31.8, an HTTP authentication service that approves every request, and a threaded fake IMAP server. Contrary to descriptions of holding LOGIN itself, the server sends LOGIN success immediately and then sleeps for 20 seconds before closing. The README claims CVE-2026-113425, an affected range of nginx 0.5.33–1.31.8, and fixes in 1.30.7/1.31.9; these claims are not independently substantiated by the supplied source. No nginx vulnerable-source analysis, patch, crash trace, or execution evidence is included. The README's claimed automatic SIGSEGV confirmation is absent from the actual script. Lab functionality also needs validation: the replacement nginx configuration contains no load_module directive, which can prevent startup when the mail module is dynamically packaged. Authentication routing and successful-login response matching must also work for the after-auth mode to reach its intended timing window. The code is an attempted denial-of-service PoC, not a verified memory-corruption exploit or a detection-only tool. No exfiltration destination or command-execution payload is present, and there is insufficient evidence to label it deliberately fake. Repository URL, revision, and archive size were not supplied; empty strings and zero represent unavailable metadata.LLCForge · Disclosed Nov 18, 2026 · python · networkPoC
FAQ

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.
Activity feed

Recent activity

121 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 in the NGINX mail-proxy module when using auth_http. Exploitation requires a mail-proxy configuration with proxy on and auth_http. 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 mail-proxy use-after-free vulnerability exploitable under certain authentication configurations. It is one of the five critical NGINX2Root vulnerabilities described as potentially enabling unauthenticated remote code execution with worker-process privileges. The advisory recommends installing patched releases and reviewing or temporarily restricting mail-proxy functionality. 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 mail proxy use-after-free vulnerability involving auth_http, rated 9.2 and 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 mail authentication proxy, affecting upstream versions 0.5.33 through 1.31.8 when proxy on and auth_http are combined. 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. Restricting mail listeners to loopback or blocking untrusted access with a firewall provides temporary mitigation. 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 activity19Community discussion across Reddit, Mastodon, and other social sources.