# CVE-2026-92388: FTP wildcard write callback mixup


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** ALPINE-CVE-2026-92388, AZL-109917, AZL-109944, AZL-110004, AZL-110163, AZL-110217, AZL-110280, BELL-CVE-2026-92388, CURL-CVE-2026-92388, DEBIAN-CVE-2026-92388, ECHO-1c20-614d-0452, GHSA-r22r-3m6c-qv5r, MINI-f66r-rrgc-5m4p, UBUNTU-CVE-2026-92388

## What is CVE-2026-92388?

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

### Official description

When an FTP wildcard `LIST` operation fails, libcurl omits the restoration
path meant for successful listings, leaving the write callback set to the
internal listing parser and the write callback data pointing directly to the
easy handle. Subsequent reuse of this handle triggers an immediate crash, and
cloning it via `curl_easy_duphandle()` copies this corrupted state into the
duplicate. If the original handle is subsequently freed, executing a transfer
on the cloned handle causes a heap use-after-free read against the dangling
handle reference; alternatively, reusing the original or cloned handle while
changing only  `CURLOPT_WRITEDATA` (and omitting `CURLOPT_WRITEFUNCTION`)
results in type confusion, forcing the internal parser to interpret incoming
server response bytes into memory at the application-supplied write data
pointer.

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


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

Upgrade to a fixed version.

## Is CVE-2026-92388 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92388 is a vulnerability in curl, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92388 in the wild and no public exploit code.

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

## Sources

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

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