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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Redhat_linux | — | No solution exists | Oct 19, 2026 | Oct 14, 2026 |
| Ubuntu | — | Upgrade libcurl3t64-gnutlsUpgrade libcurl4-openssl-devUpgrade curlUpgrade libcurl4-gnutls-devUpgrade libcurl4t64Upgrade libcurl3-nssUpgrade libcurl4Upgrade libcurl3-gnutlsUpgrade libcurl4-nss-dev | Oct 14, 2026 | Oct 14, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub