Security readout for executives and security teams
CVE-2025-14017 affects curl/libcurl when LDAPS transfers are used concurrently across threads. A TLS option change made for one threaded LDAPS transfer could leak into global state and affect other transfers being set up at the same time. The main risk is that disabling certificate verification for one transfer could unintentionally disable certificate verification for another concurrent LDAPS transfer. Exposure is most likely in applications or services that use affected curl/libcurl versions for LDAP over TLS and perform LDAPS transfers from multiple threads. Risk is higher where application logic sometimes disables TLS certificate verification for a specific transfer. Simple single-threaded curl use, non-LDAPS protocols, or deployments that never alter LDAPS TLS verification settings are less likely to be exposed based on the provided description. Medium priority. Treat as important for systems that use multi-threaded LDAPS through libcurl, especially identity, directory, authentication, or administrative tooling. Lower priority for systems that do not use LDAPS or do not use threaded libcurl transfer setup. Mitigation focus: Inventory applications, containers, and operating system packages that include curl or link against libcurl.; Prioritize systems that use LDAPS with libcurl in multi-threaded code paths.; Check curl vendor guidance and operating system or distribution advisories for the fixed version or backported patch; the bundle does not provide explicit patch-version evidence..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-567: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-14017 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N15.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- jsonCVE reference
- wwwCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unsynchronized Access to Shared Data in a Multithreaded Context
Unsynchronized Access to Shared Data in a Multithreaded Context represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
