# CVE-2026-86411: FTP connection reuse inherits client-certificate


- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** ALPINE-CVE-2026-86411, BELL-CVE-2026-86411, CURL-CVE-2026-86411, DEBIAN-CVE-2026-86411, GHSA-533v-mrfx-494r, MINI-486q-v4m4-cpqc, MINI-m772-8mvf-243g

## What is CVE-2026-86411?

CVE-2026-86411 is a critical vulnerability in curl, published on 20 Oct 2026. 

### Official description

An `ftp://` transfer configured with `CURLUSESSL_NONE` can reuse a pooled FTP
control connection that a previous easy handle upgraded with `STARTTLS` and
authenticated using a client certificate. The second handle performs neither a
new TLS handshake nor a new FTP login, so the server continues to authorize it
under the first handle's certificate identity.

Weakness: CWE-488 (Exposure of Data Element to Wrong Session)

## Which versions are affected by CVE-2026-86411?


## How do I fix CVE-2026-86411?

Upgrade to a fixed version.

## Is CVE-2026-86411 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86411 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86411 and fix it if it is affected.

What it is: CVE-2026-86411 is a critical vulnerability in curl, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86411 exists.

Affected product: 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-2026-86411/ (Markdown: https://insights.sbomify.com/CVE-2026-86411/index.md)
```

## Sources

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

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