published 20 Oct 2026 · updated 29 Oct 2026
stale SigV4 headers sent unintended
8.1HighCVSS 8.1EPSS 1%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| curl | >=7.75.0 <=7.75.0, >=7.76.0 <=7.76.0, >=7.76.1 <=7.76.1, >=7.77.0 <=7.77.0, >=7.78.0 <=7.78.0, >=7.79.0 <=7.79.0, >=7.79.1 <=7.79.1, >=7.80.0 <=7.80.0, >=7.81.0 <=7.81.0, >=7.82.0 <=7.82.0, >=7.83.0 <=7.83.0, >=7.83.1 <=7.83.1, >=7.84.0 <=7.84.0, >=7.85.0 <=7.85.0, >=7.86.0 <=7.86.0, >=7.87.0 <=7.87.0, >=7.88.0 <=7.88.0, >=7.88.1 <=7.88.1, >=8.0.0 <=8.0.0, >=8.0.1 <=8.0.1, >=8.1.0 <=8.1.0, >=8.1.1 <=8.1.1, >=8.1.2 <=8.1.2, >=8.10.0 <=8.10.0, >=8.10.1 <=8.10.1, >=8.11.0 <=8.11.0, >=8.11.1 <=8.11.1, >=8.12.0 <=8.12.0, >=8.12.1 <=8.12.1, >=8.13.0 <=8.13.0, >=8.14.0 <=8.14.0, >=8.14.1 <=8.14.1, >=8.15.0 <=8.15.0, >=8.16.0 <=8.16.0, >=8.17.0 <=8.17.0, >=8.18.0 <=8.18.0, >=8.19.0 <=8.19.0, >=8.2.0 <=8.2.0, >=8.2.1 <=8.2.1, >=8.20.0 <=8.20.0, >=8.21.0 <=8.21.0, >=8.3.0 <=8.3.0, >=8.4.0 <=8.4.0, >=8.5.0 <=8.5.0, >=8.6.0 <=8.6.0, >=8.7.0 <=8.7.0, >=8.7.1 <=8.7.1, >=8.8.0 <=8.8.0, >=8.9.0 <=8.9.0, >=8.9.1 <=8.9.1 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket