CVE-2026-71861 PUBLISHED

Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders

Assigner: GitHub_M
Reserved: 07.08.2026 Published: 18.11.2026 Updated: 18.11.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS Score: 7.4

Product Status

Vendor chainguard-dev
Product sdk
Versions
  • Version < 0.1.107 is affected

References

Problem Types

  • CWE-290: Authentication Bypass by Spoofing CWE
  • CWE-294: Authentication Bypass by Capture-replay CWE
  • CWE-347: Improper Verification of Cryptographic Signature CWE