Koffei

CVE-2026-92388

🟠 Medium

curl · 7.21.0 through 8.22.0

CVSS (Koffei note)
9.1
CVSS (v3.1, CVE List)
9.1
EPSS (2026-11-18)
0.699%
53.86th percentile

Exploitation

Probable — public PoC (SSVC: poc, CISA-ADP 2026-10-30); no exploitation reported; not in KEV. Not in the 0day "In the Wild" sheet (checked 18/11/2026). cyberveille RSS: checked 18/11/2026 (feed 19/10 to 17/11/2026), no result (automated enrichment)

Timeline

  1. 20/10/2026CVE record published (CVE List)
  2. 18/11/2026CERT-FR relays Oracle's off-cycle November update for six product lines

Risk

9.1 Critical (v3.1, CISA-ADP) — AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H, EPSS 0.699%, 53.74th percentile, scored 2026-11-17 (CWE-416: After a failed FTP wildcard LIST, libcurl leaves the write callback and write data pointing at internal state; reusing or duplicating the handle can crash, cause a use-after-free read, or type confusion that writes server bytes to app memory.)

Fix

Yes — Oracle MySQL: Oracle cspunov2026 (17/11/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.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H