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.
References
Configurations
No configuration.
History
30 Oct 2026, 13:20
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-200 | |
| References | () https://hackerone.com/reports/4022568 - | |
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 8.1 |
20 Oct 2026, 21:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-20 21:17
Updated : 2026-10-30 13:20
NVD link : CVE-2026-92389
Mitre link : CVE-2026-92389
CVE.ORG link : CVE-2026-92389
JSON object : View
Products Affected
No product.
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor
