CVE-2025-14017 | broken TLS options for threaded LDAPS

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: 2026-01-08 Last update: 2026-01-27 Assigner: 2499f714-1537-4658-8207-48ae4bb9eae9 Source: 2499f714-1537-4658-8207-48ae4bb9eae9
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-14017 is rated Low Risk (25.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-14017

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-08 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-14017

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.3 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.0 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-14017

OS Trackers for CVE-2025-14017

vendor priority summary link
alpine — CVE-2025-14017: 1 source package rows (curl); 280 state rows across 6 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, 3.23-main, edge-main); fixed 1, open 279. https://security.alpinelinux.org/vuln/CVE-2025-14017
debian unimportant CVE-2025-14017 unimportant priority: Debian including 1 source packages (curl), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2025-14017
redhat medium — https://access.redhat.com/security/cve/CVE-2025-14017
suse medium CVE-2025-14017 severity moderate: SUSE including 342 source package names (1.1.0-1.13:libcurl4-8.14.1-150700.7.11.1, 13.2-9.63:curl-8.14.1-slfo.1.1_5.1, …), 824 product×package rows across 242 product lines (Container private-registry/harbor-trivy-adapter, Container suse/ltss/sle12.5/sles12sp5, … (242 product lines)): Fixed 587, Known Affected 231, First Fixed 6. https://www.suse.com/security/cve/CVE-2025-14017/
ubuntu medium CVE-2025-14017 medium priority: Ubuntu including 1 source packages (curl), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): released 8, ignored 1. https://ubuntu.com/security/CVE-2025-14017

Affected software / configurations for CVE-2025-14017

Vendor Product Version Raw CPE
haxx curl >= 7.17.0, < 8.18.0 cpe:2.3:a:haxx:curl:*:*:*:*:*:*:*:*

References for CVE-2025-14017

cvelogic Threat Intelligence