curl libcurl up to 8.22.0 Internal Listing Parser curl_easy_duphandle use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.3 | $0-$5k | 0.90+ |
Summary
A vulnerability described as critical has been identified in curl libcurl. Affected by this vulnerability is the function curl_easy_duphandle of the component Internal Listing Parser. The manipulation results in use after free.
This vulnerability is cataloged as CVE-2026-92388. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability, which was classified as critical, was found in curl libcurl. Affected is the function curl_easy_duphandle of the component Internal Listing Parser. The manipulation with an unknown input leads to a use after free vulnerability. CWE is classifying the issue as CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at curl.se. This vulnerability is traded as CVE-2026-92388 since 09/16/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 10/20/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
- 7.0
- 7.1
- 7.2
- 7.3
- 7.4
- 7.5
- 7.6
- 7.7
- 7.8
- 7.9
- 7.10
- 7.11
- 7.12
- 7.13
- 7.14
- 7.15
- 7.16
- 7.17
- 7.18
- 7.19
- 7.20
- 7.21
- 7.21.0
- 7.21.1
- 7.21.2
- 7.21.3
- 7.21.4
- 7.21.5
- 7.21.6
- 7.21.7
- 7.22
- 7.22.0
- 7.23
- 7.23.0
- 7.23.1
- 7.24
- 7.24.0
- 7.25
- 7.25.0
- 7.26
- 7.26.0
- 7.27
- 7.27.0
- 7.28
- 7.28.0
- 7.28.1
- 7.29
- 7.29.0
- 7.30
- 7.30.0
- 7.31
- 7.31.0
- 7.32
- 7.32.0
- 7.33
- 7.33.0
- 7.34
- 7.34.0
- 7.35
- 7.35.0
- 7.36
- 7.36.0
- 7.37
- 7.37.0
- 7.37.1
- 7.38
- 7.38.0
- 7.39
- 7.39.0
- 7.40
- 7.40.0
- 7.41
- 7.41.0
- 7.42
- 7.42.0
- 7.42.1
- 7.43
- 7.43.0
- 7.44
- 7.44.0
- 7.45
- 7.45.0
- 7.46
- 7.46.0
- 7.47
- 7.47.0
- 7.47.1
- 7.48
- 7.48.0
- 7.49
- 7.49.0
- 7.49.1
- 7.50
- 7.50.0
- 7.50.1
- 7.50.2
- 7.50.3
- 7.51
- 7.51.0
- 7.52
- 7.52.0
- 7.52.1
- 7.53
- 7.53.0
- 7.53.1
- 7.54
- 7.54.0
- 7.54.1
- 7.55
- 7.55.0
- 7.55.1
- 7.56
- 7.56.0
- 7.56.1
- 7.57
- 7.57.0
- 7.58
- 7.58.0
- 7.59
- 7.59.0
- 7.60
- 7.60.0
- 7.61
- 7.61.0
- 7.61.1
- 7.62
- 7.62.0
- 7.63
- 7.63.0
- 7.64
- 7.64.0
- 7.64.1
- 7.65
- 7.65.0
- 7.65.1
- 7.65.2
- 7.65.3
- 7.66
- 7.66.0
- 7.67
- 7.67.0
- 7.68
- 7.68.0
- 7.69
- 7.69.0
- 7.69.1
- 7.70
- 7.70.0
- 7.71
- 7.71.0
- 7.71.1
- 7.72
- 7.72.0
- 7.73
- 7.73.0
- 7.74
- 7.74.0
- 7.75
- 7.75.0
- 7.76
- 7.76.0
- 7.76.1
- 7.77
- 7.77.0
- 7.78
- 7.78.0
- 7.79
- 7.79.0
- 7.79.1
- 7.80
- 7.80.0
- 7.81
- 7.81.0
- 7.82
- 7.82.0
- 7.83
- 7.83.0
- 7.83.1
- 7.84
- 7.84.0
- 7.85
- 7.85.0
- 7.86
- 7.86.0
- 7.87
- 7.87.0
- 7.88.0
- 7.88.1
- 8.0
- 8.0.0
- 8.0.1
- 8.1
- 8.1.0
- 8.1.1
- 8.1.2
- 8.2
- 8.2.0
- 8.2.1
- 8.3
- 8.3.0
- 8.4
- 8.4.0
- 8.5
- 8.5.0
- 8.6
- 8.6.0
- 8.7
- 8.7.0
- 8.7.1
- 8.8
- 8.8.0
- 8.9
- 8.9.0
- 8.9.1
- 8.10
- 8.10.0
- 8.10.1
- 8.11
- 8.11.0
- 8.11.1
- 8.12
- 8.12.0
- 8.12.1
- 8.13
- 8.13.0
- 8.14
- 8.14.0
- 8.14.1
- 8.15
- 8.15.0
- 8.16
- 8.16.0
- 8.17
- 8.17.0
- 8.18
- 8.18.0
- 8.19
- 8.19.0
- 8.20
- 8.20.0
- 8.21
- 8.21.0
- 8.22.0
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 7.3
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
09/16/2026 CVE reserved10/20/2026 Advisory disclosed
10/20/2026 VulDB entry created
10/20/2026 VulDB entry last update
Sources
Advisory: curl.seStatus: Confirmed
CVE: CVE-2026-92388 (🔒)
GCVE (CVE): GCVE-0-2026-92388
GCVE (VulDB): GCVE-100-422994
Entry
Created: 10/20/2026 22:43Changes: 10/20/2026 22:43 (54)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.