# CVE-2025-14819: OpenSSL partial chain store policy bypass

> Attackers can bypass TLS partial chain restrictions in libcurl by reusing handles, potentially accepting untrusted certificates.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **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-14819, BELL-CVE-2025-14819, CURL-CVE-2025-14819, DEBIAN-CVE-2025-14819, ECHO-2c28-953d-b5a0, GHSA-vqhr-m87q-9jqh, JLSEC-2026-429, MINI-qg6h-2m68-9vvh, ROOT-OS-DEBIAN-12-CVE-2025-14819, UBUNTU-CVE-2025-14819

## What is CVE-2025-14819?

CVE-2025-14819 is a medium-severity vulnerability in Haxx Curl, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

When doing TLS related transfers with reused easy or multi handles and
altering the `CURLSSLOPT_NO_PARTIALCHAIN` option, libcurl could accidentally
reuse a CA store cached in memory for which the partial chain option was
reversed. Contrary to the user's wishes and expectations. This could make
libcurl find and accept a trust chain that it otherwise would not.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Haxx Curl.

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

Upgrade to a fixed version.

## Is CVE-2025-14819 being exploited?

There is no known exploitation of CVE-2025-14819 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-14819 and fix it if it is affected.

What it is: CVE-2025-14819 is a medium-severity vulnerability in Haxx Curl, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-14819 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-14819/ (Markdown: https://insights.sbomify.com/CVE-2025-14819/index.md)
```

## Sources

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

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