Is CVE-2026-92388 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-92388 being exploited in the wild.

How severe is CVE-2026-92388?

Informational severity, published 20 October 2026.

Which products and versions are affected?

Curl Libcurl 7.21.0 to 8.22.0, excluding 8.14.3, 8.16.2, 8.20.2.

Is there a fix for CVE-2026-92388?

Yes: fixed in libcurl 8.23.0, 8.20.2 (8.20.x branch), 8.16.2 (8.16.x branch), 8.14.3 (8.14.x branch). Until then: Never reuse easy handles for or after FTP wildcard matches; alternatively, apply the patches identified in commits ba8f8a7f27a5c5e19e4ef212 and b85acacec9b38442741bb019bc9. [{"kind":"disclosed","at":"2026-09-11","note":"Issue reported to curl project"},{"kind":"patched","at":"2026-10-14","note":"curl 8.23.0 released with fix, coordinated with advisory publication"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-92388 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-92388?

Check whether you run Curl Libcurl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-92388: curl FTP wildcard write callback mixup

CVE-2026-92388 · Severity: info · Published 2026-10-20

libcurl is a widely-used library for transferring data over networks using protocols like FTP and HTTP. When an FTP wildcard listing operation fails and the application reuses the same handle, libcurl may crash immediately, trigger memory corruption, or allow a type confusion attack that forces the FTP parser to write data to an attacker-controlled memory location. This affects applications using FTP wildcard functionality, potentially leading to denial of service or information disclosure.

Technologies: Curl Libcurl. Vendors: Curl.

Quick answers

Is CVE-2026-92388 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92388 being exploited in the wild.
How severe is CVE-2026-92388?: Informational severity, published 20 October 2026.
Which products and versions are affected?: Curl Libcurl 7.21.0 to 8.22.0, excluding 8.14.3, 8.16.2, 8.20.2.
Is there a fix for CVE-2026-92388?: Yes: fixed in libcurl 8.23.0, 8.20.2 (8.20.x branch), 8.16.2 (8.16.x branch), 8.14.3 (8.14.x branch). Until then: Never reuse easy handles for or after FTP wildcard matches; alternatively, apply the patches identified in commits ba8f8a7f27a5c5e19e4ef212 and b85acacec9b38442741bb019bc9.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-09-11","note":"Issue reported to curl project"},{"kind":"patched","at":"2026-10-14","note":"curl 8.23.0 released with fix, coordinated with advisory publication"}] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-92388 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-92388?: Check whether you run Curl Libcurl at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: libcurl 8.23.0, 8.20.2 (8.20.x branch), 8.16.2 (8.16.x branch), 8.14.3 (8.14.x branch)

Never reuse easy handles for or after FTP wildcard matches; alternatively, apply the patches identified in commits ba8f8a7f27a5c5e19e4ef212 and b85acacec9b38442741bb019bc9.</anigation> <parameter name="timeline">[{"kind":"disclosed","at":"2026-09-11","note":"Issue reported to curl project"},{"kind":"patched","at":"2026-10-14","note":"curl 8.23.0 released with fix, coordinated with advisory publication"}]

Technical details

A use-after-free vulnerability (CWE-416) in libcurl's FTP wildcard implementation occurs when a failed LIST operation leaves internal write callbacks and data pointers in an inconsistent state. Subsequent reuse of the curl easy handle, cloning via curl_easy_duphandle(), or changing CURLOPT_WRITEDATA without CURLOPT_WRITEFUNCTION can trigger immediate crashes, heap use-after-free reads, or type confusion attacks. The flaw requires CURLOPT_FTP_WILDCARD to be enabled and does not affect the curl command-line tool.

Affected products

curl libcurl 7.21.0 to 8.22.0, excluding 8.14.3, 8.16.2, 8.20.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.