Microsoft security update for CVE-2025-5025
🔗 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-5025. This page also shows what EchelonGraph holds for CVE-2025-5025, 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 products12
- azl3 cmake 3.30.3-6 on Azure Linux 3.0
- azl3 curl 8.11.1-3 on Azure Linux 3.0
- azl3 mysql 8.0.41-1 on Azure Linux 3.0
- azl3 rust 1.75.0-14 on Azure Linux 3.0
- azl3 rust 1.86.0-1 on Azure Linux 3.0
- azl3 tensorflow 2.16.1-9 on Azure Linux 3.0
- cbl2 curl 8.8.0-6 on CBL Mariner 2.0
- cbl2 curl 8.8.0-6 on CBL-Mariner 2.0
- cbl2 mysql 8.0.41-1 on CBL Mariner 2.0
- cbl2 mysql 8.0.41-1 on CBL-Mariner 2.0
- cbl2 rust 1.72.0-10 on CBL Mariner 2.0
- cbl2 rust 1.72.0-10 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 1 update
1 row: 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 | 3.30.3-6 |
🧭 EchelonGraph on CVE-2025-5025
- EchelonGraph score
- 4.8 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
libcurl supports *pinning* of the server certificate public key for HTTPS transfers. Due to an omission, this check is not performed when connecting with QUIC for HTTP/3, when the TLS backend is wolfSSL. Documentation says the option works with wolfSSL, failing to specify that it does not for QUIC and HTTP/3. Since pinning makes the transfer succeed if the pin is fine, users could unwittingly connect to an impostor server without noticing.
Published by curl, the CVE Numbering Authority that assigned CVE-2025-5025, 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).