CVE-2026-71861 Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: no · technical impact: total
- Technology
- Cloud Platforms
Description
The Chainguard SDK is a public Go SDK for integrating with the Chainguard platform. Prior to 0.1.107, auth/aws.VerifyToken trusts the Chainguard-Audience and Chainguard-Identity headers without requiring those headers to be covered by AWS SigV4 SignedHeaders. An attacker with a fresh STS GetCallerIdentity request signed by a victim can rewrite the unsigned binding headers and replay the proof to another relying party, causing the relying party to authenticate the victim’s AWS identity for an attacker-chosen audience and identity. Code that only uses auth/aws.GenerateToken is unaffected because the generator signs the binding headers, and exploitation requires a signed request within its validity window. This issue is fixed in version 0.1.107.
Upgrade path
2 packages: 1 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| chainguard.dev/sdk(Go) | < 0.1.107; <= 0.1.106 | 0.1.107 | Fixed |
| chainguard-dev sdk | = < 0.1.107 | No fix listed | Versions listed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| chainguard-dev sdk | = < 0.1.107 | No fix listed |
| chainguard.dev/sdk(Go) | <= 0.1.106 | No fix listed |
| chainguard.dev/sdk(Go) | < 0.1.107 | 0.1.107 |
References
- https://github.com/chainguard-dev/sdk/security/advisories/GHSA-wq26-3j2m-4hvv vendor-advisory
- https://github.com/chainguard-dev/sdk/commit/d27997d62aaffe85f905cce4cbe8cdebbd5e24eb patch
- https://github.com/chainguard-dev/sdk/releases/tag/v0.1.107
- nvd.nist.gov third-party-advisory vendor-advisory
- github.com
- github.com product
- ENISA EUVD EUVD-2026-129009 third-party-advisory