CVE-2025-14017 is a libcurl vulnerability affecting multi-threaded LDAPS (LDAP over TLS) transfers when libcurl is built with the legacy non-Windows LDAP backend (lib/ldap.c). In affected versions, changing TLS-related options for one transfer can inadvertently modify shared global state, causing those TLS settings to affect other concurrently initialized LDAPS transfers in different threads. As described in the advisory, this can result in per-transfer settings such as disabled certificate verification being unintentionally applied to unrelated transfers. The issue is highly timing-sensitive and stems from unsynchronized access to shared data in a multithreaded context. The flaw affects curl/libcurl versions 7.17.0 through 8.17.0 and is fixed in 8.18.0. Builds using OpenLDAP or WinLDAP are not affected, and the curl command-line tool is not affected.
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.
24 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.