# CVE-2026-92389: TFTP direction confusion


- **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-92389, AZL-109929, AZL-109950, AZL-110013, AZL-110190, AZL-110235, AZL-110301, BELL-CVE-2026-92389, CURL-CVE-2026-92389, DEBIAN-CVE-2026-92389, ECHO-d5aa-0961-19b4, GHSA-9rxv-c97x-mrjr, MINI-xrq5-qrj4-5393, UBUNTU-CVE-2026-92389

## What is CVE-2026-92389?

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

### Official description

libcurl's TFTP state machine fails to validate state transitions against the
requested transfer direction, accepting opening server responses for both
reads and writes interchangeably. A malicious TFTP server can respond to a
download request in a way that forces the client into transmit mode, prompting
libcurl to consume and transmit data from the handle's persistent
`CURLOPT_READDATA` pointer - including data remaining from unrelated prior
operations, such as an HTTP POST request executed on a reused handle.

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


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

Upgrade to a fixed version.

## Is CVE-2026-92389 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92389 is a vulnerability in curl, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92389 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-92389/ (Markdown: https://insights.sbomify.com/CVE-2026-92389/index.md)
```

## Sources

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

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