CVE-2026-92388

FTP wildcard write callback mixup

State
Published
Severity
9.1 Critical
Published
Oct 20, 2026
Updated
Oct 30, 2026
Reserved
Sep 16, 2026

Read the record on cve.org

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.

Scores

CVSSScoreVectorSource
3.19.1 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HCISA-ADP

Weaknesses

Affected Products

ProductVersions
curlcurl
  • 8.22.0 through 8.22.0Affected
  • 8.21.0 through 8.21.0Affected
  • 8.20.0 through 8.20.0Affected
  • 8.19.0 through 8.19.0Affected
  • 8.18.0 through 8.18.0Affected
  • 8.17.0 through 8.17.0Affected
  • 8.16.0 through 8.16.0Affected
  • 8.15.0 through 8.15.0Affected
  • 8.14.1 through 8.14.1Affected
  • 8.14.0 through 8.14.0Affected
  • 8.13.0 through 8.13.0Affected
  • 8.12.1 through 8.12.1Affected
  • 8.12.0 through 8.12.0Affected
  • 8.11.1 through 8.11.1Affected
  • 8.11.0 through 8.11.0Affected
  • 8.10.1 through 8.10.1Affected
  • 8.10.0 through 8.10.0Affected
  • 8.9.1 through 8.9.1Affected
  • 8.9.0 through 8.9.0Affected
  • 8.8.0 through 8.8.0Affected
  • 8.7.1 through 8.7.1Affected
  • 8.7.0 through 8.7.0Affected
  • 8.6.0 through 8.6.0Affected
  • 8.5.0 through 8.5.0Affected
  • 8.4.0 through 8.4.0Affected
  • and 108 more versions

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.