CVE-2026-92388FTP wildcard write callback mixup
Updated under an hour ago ()
Does this affect you?
It affects curl. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- CWE-416
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- curl
- NVD analysis
- Received
- Record last updated
- Oct 20, 2026
- First seen by InfoSec Signals
- Oct 20, 2026
Affected products
curl curl curl:curl (from the name) | from 8.22.0 through 8.22.0; from 8.21.0 through 8.21.0; from 8.20.0 through 8.20.0; from 8.19.0 through 8.19.0; from 8.18.0 through 8.18.0; from 8.17.0 through 8.17.0; from 8.16.0 through 8.16.0; from 8.15.0 through 8.15.0; and 125 more ranges | CNA record |
References
- https://curl.se/docs/CVE-2026-92388.json
- https://curl.se/docs/CVE-2026-92388.html
- https://hackerone.com/reports/4022070
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.