CVE-2025-14017MediumMicrosoft CVSS 5.9CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Microsoft security update for CVE-2025-14017

Published
June 2, 2026
Last Modified
—

🔗 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-14017. This page also shows what EchelonGraph holds for CVE-2025-14017, 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 products8

  • azl3 cmake 3.30.3-10 on Azure Linux 3.0
  • azl3 cmake 3.30.3-11 on Azure Linux 3.0
  • azl3 curl 8.11.1-4 on Azure Linux 3.0
  • azl3 curl 8.11.1-5 on Azure Linux 3.0
  • cbl2 cmake 3.21.4-20 on CBL Mariner 2.0
  • cbl2 cmake 3.21.4-21 on CBL Mariner 2.0
  • cbl2 curl 8.8.0-7 on CBL Mariner 2.0
  • cbl2 curl 8.8.0-8 on CBL Mariner 2.0

✅ Updates Microsoft lists: 4 updates

4 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update3.30.3-11
—Security Update3.21.4-21
—Security Update8.11.1-5
—Security Update8.8.0-8

🧭 EchelonGraph on CVE-2025-14017

EchelonGraph score
6.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

When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers. Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.

Published by curl, the CVE Numbering Authority that assigned CVE-2025-14017, 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).

🔗 References (2)