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.