# CVE-2025-14017: broken TLS options for threaded LDAPS

> Concurrent LDAPS transfers in libcurl may unintentionally disable TLS certificate verification globally, bypassing security checks.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Jan 2026
- **Updated:** 15 Sep 2026
- **Also known as:** ALPINE-CVE-2025-14017, AZL-73676, AZL-73736, AZL-73740, AZL-73743, BELL-CVE-2025-14017, CURL-CVE-2025-14017, DEBIAN-CVE-2025-14017, ECHO-8091-7fb3-2ea0, GHSA-jh4h-2cg6-889h, JLSEC-2026-427, MINI-wggm-33cc-6qg6, ROOT-OS-DEBIAN-12-CVE-2025-14017, ROOT-OS-DEBIAN-13-CVE-2025-14017, SUSE-SU-2026:0077-1, SUSE-SU-2026:0078-1, SUSE-SU-2026:0119-1, SUSE-SU-2026:0221-1, SUSE-SU-2026:20347-1, SUSE-SU-2026:20358-1, UBUNTU-CVE-2025-14017

## What is CVE-2025-14017?

CVE-2025-14017 is a medium-severity vulnerability in Haxx Curl, published on 8 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-567 (Unsynchronized Access to Shared Data in a Multithreaded Context)

## Which versions are affected by CVE-2025-14017?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `curl` | SUSE:Linux Enterprise Micro 5.2 | All versions | 8.14.1-150200.4.100.1 |
| `curl` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 8.14.1-150700.7.11.1 |
| `curl` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 8.0.1-11.114.1 |
| `curl` | SUSE:Linux Micro 6.0 | All versions | 8.14.1-4.1 |
| `curl` | SUSE:Linux Micro 6.1 | All versions | 8.14.1-slfo.1.1_5.1 |
| `curl` | openSUSE:Leap 15.6 | All versions | 8.14.1-150600.4.37.1 |

Products: Haxx Curl.

## How do I fix CVE-2025-14017?

Upgrade to a fixed version.

## Is CVE-2025-14017 being exploited?

There is no known exploitation of CVE-2025-14017 in the wild and no public exploit code.

## Other vulnerabilities in Haxx Curl

- [CVE-2026-19931](https://insights.sbomify.com/CVE-2026-19931/): Negotiate ambient user conn reuse (critical 9.8)
- [CVE-2026-10536](https://insights.sbomify.com/CVE-2026-10536/): HTTP/2 stream-dependency tree UAF (critical 9.8)
- [CVE-2026-11856](https://insights.sbomify.com/CVE-2026-11856/): cross-origin Digest auth state leak (critical 9.8)
- [CVE-2026-8925](https://insights.sbomify.com/CVE-2026-8925/): SASL double-free (critical 9.8)
- [CVE-2026-9079](https://insights.sbomify.com/CVE-2026-9079/): stale proxy password leak (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14017 and fix it if it is affected.

What it is: CVE-2025-14017 is a medium-severity vulnerability in Haxx Curl, published on 8 Jan 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-14017 in the wild and no public exploit code.

Affected product: Haxx Curl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14017/ (Markdown: https://insights.sbomify.com/CVE-2025-14017/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14017
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14017
- OSV: https://osv.dev/vulnerability/CVE-2025-14017

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14017/
Summaries are generated and may contain mistakes; the official description above is the record.