CVE-2025-14017 is a medium-severity vulnerability in libcurl affecting multi-threaded LDAPS transfers when libcurl is built with the legacy non-Windows LDAP backend. During concurrent LDAP over TLS operations, changes to TLS-related options intended for a single transfer can be applied through shared global state rather than remaining scoped to the calling thread or transfer. As a result, one thread's TLS configuration can inadvertently affect other concurrently initialized LDAPS transfers. A documented consequence is that disabling certificate verification for one transfer may unintentionally disable verification for other threads as well. The issue is highly timing-sensitive and is limited to libcurl versions 7.17.0 through 8.17.0 using the legacy backend; builds using OpenLDAP or WinLDAP are not affected, and the curl command-line tool is not impacted.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
28 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.