Microsoft security update for CVE-2026-87866 — azl3
🔗 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-2026-87866. This page also shows what EchelonGraph holds for CVE-2026-87866, 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 products6
- azl3 cmake 3.30.3-15 on Azure Linux 3.0
- azl3 curl 8.11.1-11 on Azure Linux 3.0
- azl3 mysql 8.0.46-2 on Azure Linux 3.0
- azl3 rust 1.75.0-31 on Azure Linux 3.0
- azl3 rust 1.96.1-2 on Azure Linux 3.0
- azl3 tensorflow 2.16.1-11 on Azure Linux 3.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 | — |
🧭 EchelonGraph on CVE-2026-87866
- EchelonGraph score
- 9.1 CRITICAL
- 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
When built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field - extracts and matches a different embedded key, incorrectly authorizing the pinned public key.
Published by curl, the CVE Numbering Authority that assigned CVE-2026-87866, 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).