An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously wasused to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. The problem exists in the logic for a reused handle when it is (expected to be) changed from a PUT to a POST.
https://support.apple.com/kb/HT213845
https://support.apple.com/kb/HT213844
https://support.apple.com/kb/HT213843
https://security.netapp.com/advisory/ntap-20230609-0009/
https://security.gentoo.org/glsa/202310-12
https://lists.debian.org/debian-lts-announce/2023/12/msg00015.html
https://hackerone.com/reports/1954658
http://seclists.org/fulldisclosure/2023/Jul/52