CVE-2025-53859: NGINX Open Source and NGINX Plus have a vulnerability in the ngx_mail_smtp_module that might allow an unauthenticated attacker to over-read NGINX SMTP authentication process memory; as a result,...
Low CVSS 3.7
- CVE id
- CVE-2025-53859
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| NGINX Runtimes and servers |
>= 0.7.22, < 1.29.1 | 1.29.1 |
| NGINX Plus Runtimes and servers |
>= 30, < 31 >= 31, < 32 >= 32, < 33 >= 32.1, < 32.2 >= 32.2, < 32.3 >= 33, < 34 >= 33.1, < 33.2 >= 33.2, < 33.3 >= 34, < 35 >= 34.1, < 34.2 |
31, 32, 32.2, 32.3, 33, 33.2, 33.3, 34, 34.2, 35 |
How to fix it
NGINX (Runtimes and servers)
Upgrade NGINX to 1.29.1 or later.
nginx -v
- Install the patched NGINX release of your branch (the nginx image tag, the nginx.org packages, or your distribution's security update) and restart NGINX; with OpenResty, upgrade to the OpenResty release built on it.
NGINX Plus (Runtimes and servers)
Upgrade NGINX Plus to the fixed release of the line you run: 31, 32, 32.2, 32.3, 33, 33.2, 33.3, 34, 34.2, 35.
nginx -v
- Upgrade NGINX Plus to the patched release from the F5 repository (or your nginx-plus image) and restart it.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
NGINX Open Source and NGINX Plus have a vulnerability in the ngxmailsmtpmodule that might allow an unauthenticated attacker to over-read NGINX SMTP authentication process memory; as a result, the server side may leak arbitrary bytes sent in a request to the authentication server. This issue happens during the NGINX SMTP authentication process and requires the attacker to make preparations against the target system to extract the leaked data. The issue affects NGINX only if (1) it is built with the ngxmailsmtpmodule, (2) the smtp_auth directive is configured with method "none," and (3) the authentication server returns the "Auth-Wait" response header.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.