VYPR
← All advisories
Unrated severityNVD Advisory· Published Dec 5, 2022· Updated Feb 13, 2026

CVE-2022-32221

CVE-2022-32221

Description

When reusing a libcurl handle from PUT to POST, the read callback may be erroneously invoked, potentially causing data corruption or memory safety issues.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

When reusing a libcurl handle from PUT to POST, the read callback may be erroneously invoked, potentially causing data corruption or memory safety issues.

Vulnerability

In libcurl, when an easy handle is reused after a PUT request that used CURLOPT_READFUNCTION, and then a POST request is made with CURLOPT_POSTFIELDS set, libcurl may incorrectly still use the read callback to ask for data to send. This affects versions prior to 7.86.0. The bug is in the logic for handle reuse when changing from PUT to POST.

Exploitation

An attacker would need to control the application's use of libcurl such that a handle is reused from a PUT to a POST. The application must have set CURLOPT_READFUNCTION for the PUT and then set CURLOPT_POSTFIELDS for the POST. No special network position is required; the vulnerability is in the client-side logic. The attacker could potentially cause the application to send wrong data or trigger use-after-free if the callback provides unexpected data.

Impact

Successful exploitation could lead to sending incorrect data in the POST request, or memory corruption (use-after-free) leading to information disclosure or arbitrary code execution depending on the application's memory layout. The impact is limited to the context of the application using libcurl.

Mitigation

Fixed in libcurl version 7.86.0. Apple addressed this in macOS Ventura 13.2 and macOS Monterey 12.6.3 by updating curl to 7.86.0 [3][4]. Users should update to the latest version of libcurl or apply the OS updates.

References
  1. Full Disclosure: APPLE-SA-2023-01-23-4 macOS Ventura 13.2
  2. Full Disclosure: APPLE-SA-2023-01-23-5 macOS Monterey 12.6.3

AI Insight generated on May 24, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

57

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

11

News mentions

0

No linked articles in our index yet.