Data exposure or crashes via stale upload state
Published Dec 5, 2022 · Updated Feb 13, 2026
Expected behavior violation in curl libcurl 7.7 through 7.85.0 allows attackers to expose data or crash applications via unspecified vectors. The CURLOPT_POSTFIELDS branch in Curl_vsetopt leaves data->set.upload enabled from a prior PUT, so a reused easy handle invokes the stale read callback during a later POST. Reachability requires application code that reuses a handle after PUT while mixing CURLOPT_READFUNCTION with CURLOPT_POSTFIELDS; the curl command-line tool cannot trigger it.
Summary
What happened
Expected behavior violation in curl libcurl 7.7 through 7.85.0 allows attackers to expose data or crash applications via unspecified vectors. The CURLOPT_POSTFIELDS branch in Curl_vsetopt leaves data->set.upload enabled from a prior PUT, so a reused easy handle invokes the stale read callback during a later POST. Reachability requires application code that reuses a handle after PUT while mixing CURLOPT_READFUNCTION with CURLOPT_POSTFIELDS; the curl command-line tool cannot trigger it.
The record
- CVE
- CVE-2022-32221
- Published
- Dec 5, 2022
- Updated
- Feb 13, 2026
- Vendor
- curl
- Product
- libcurl
- Classifications
- CWE-440
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Dec 5, 2022CVE publishedPublication date reported by the CVE source.
- Feb 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in 7.86.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo