CVE-2026-113425

NGINX ngx_mail_proxy_module vulnerability

Published Nov 18, 2026 CVSS 4.0 · 9.2 Critical EPSS n/a KEV · Not listed
Description
When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.

Impact:
A remote unauthenticated attacker may crash an nginx worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact. There is no control plane exposure; this is a data plane issue only.



Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Analysis

AI-generated

Technical impact

A use‑after‑free flaw exists in the nginx worker process when NGINX is configured as a mail proxy. Undisclosed traffic can trigger memory corruption, allowing an attacker to crash the worker or execute code on systems without Address Space Layout Randomization. The impact is therefore a potential remote code execution or service disruption, limited to the data plane with no control‑plane exposure.

Affected Systems

The issue affects both NGINX Open Source and NGINX Plus deployments that run the mail proxy module. No specific version range is supplied, so all actively supported releases that can be configured as a mail proxy are potentially vulnerable until a patch is applied.

Risk and Exploitability

The CVSS score of 9.2 indicates a severe risk. Because the EPSS score is not available and the vulnerability is not listed in CISA’s KEV catalog, the precise prevalence of exploitation is unclear. The likely attack vector is a network‑based one, where an unauthenticated attacker sends crafted mail traffic to a mail‑proxy listener. If ASLR is disabled or can be bypassed, remote code execution can be achieved; otherwise only a denial of service is possible.

Remediation

Vendor Workaround

Restrict listeners to trusted networks.


OpenCVE Recommended Actions

  • Upgrade to the latest verified NGINX release that contains the fix for the mail proxy use‑after‑free bug.
  • If an upgrade is not yet possible, restrict the mail proxy listener to trusted internal networks only and block all external connections.
  • Ensure that Address Space Layout Randomization is enabled on the operating system to reduce the chance of successful remote code execution.

Generated by OpenCVE AI on November 18, 2026 at 23:42 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared F5
F5 nginx Open Source
F5 nginx Plus
Vendors & Products F5
F5 nginx Open Source
F5 nginx Plus
Type Values Removed Values Added
Description When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: A remote unauthenticated attacker may crash an nginx worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Title NGINX ngx_mail_proxy_module vulnerability
Weaknesses CWE-416
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.2, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
f5
Published
Updated
Nov 18, 2026, 4:50 PM
Reserved
Nov 9, 2026, 6:42 PM
Status
Received
Published
Nov 18, 2026, 4:17 PM
Modified
Nov 18, 2026, 5:17 PM