Setting `CURLOPT_AWS_SIGV4` to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an `Authorization: AWS4-HMAC-SHA256` header to whatever URL isset next, leaking state information.
https://hackerone.com/reports/3973135
https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-105274