Microsoft security update for CVE-2025-23085
🔗 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-23085. This page also shows what EchelonGraph holds for CVE-2025-23085, 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 products5
- azl3 nodejs 20.14.0-5 on Azure Linux 3.0
- azl3 nodejs 20.14.0-8 on Azure Linux 3.0
- cbl2 nodejs18 18.20.3-3 on CBL Mariner 2.0
- cbl2 nodejs18 18.20.3-6 on CBL Mariner 2.0
- cbl2 nodejs18 18.20.3-6 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 | 20.14.0-5 |
| — | Security Update | 18.20.3-3 |
🧭 EchelonGraph on CVE-2025-23085
- EchelonGraph score
- 5.3 MEDIUM
- 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
A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.
Published by HackerOne, the CVE Numbering Authority that assigned CVE-2025-23085, 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).