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.
References
Configurations
No configuration.
History
29 Oct 2026, 19:17
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-201 | |
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 8.1 |
| References | () https://hackerone.com/reports/3973135 - |
20 Oct 2026, 20:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-20 20:17
Updated : 2026-10-29 19:17
NVD link : CVE-2026-86409
Mitre link : CVE-2026-86409
CVE.ORG link : CVE-2026-86409
JSON object : View
Products Affected
No product.
CWE
CWE-201
Insertion of Sensitive Information Into Sent Data
