Microsoft security update for CVE-2025-53859
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-53859. This page also shows what EchelonGraph holds for CVE-2025-53859, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products4
- azl3 nginx 1.25.4-4 on Azure Linux 3.0
- azl3 nginx 1.25.4-5 on Azure Linux 3.0
- cbl2 nginx 1.22.1-13 on CBL Mariner 2.0
- cbl2 nginx 1.22.1-14 on CBL Mariner 2.0
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 1.22.1-14 |
| — | Security Update | 1.25.4-5 |
🧭 EchelonGraph on CVE-2025-53859
- EchelonGraph score
- 3.7 LOW
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
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, 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 ngx_mail_smtp_module, (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.
Published by F5, Inc., the CVE Numbering Authority that assigned CVE-2025-53859, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).