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.
Fix
Vendor advisories in the News 1
- USN-8932-1: curl vulnerabilities Ubuntu Security Notices · 2026-10-14
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 4
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-29 18:33
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-22 17:21
- StatusReceived → PublishedNVD modified 2026-10-20 19:57
- First seenunscoredNVD modified 2026-10-20 20:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.