DEV Community

CVE Reports
CVE Reports

Posted on Originally published at cvereports.com

CVE-2026-71861: CVE-2026-71861: Authentication Bypass via Unsigned Binding Headers in Chainguard Go SDK

CVE-2026-71861: Authentication Bypass via Unsigned Binding Headers in Chainguard Go SDK

Vulnerability ID: CVE-2026-71861
CVSS Score: 7.4
Published: 2026-11-18

CVE-2026-71861 (GHSA-wq26-3j2m-4hvv) is a high-severity authentication bypass and cryptographic signature-binding replay vulnerability in the Chainguard Go SDK (chainguard.dev/sdk / github.com/chainguard-dev/sdk) affecting versions prior to v0.1.107. The vulnerability resides in the auth/aws.VerifyToken function, which validates AWS STS GetCallerIdentity requests signed with AWS Signature Version 4 (SigV4) to authenticate AWS workloads. Prior to version v0.1.107, VerifyToken verified the values of custom HTTP binding headers (Chainguard-Audience and Chainguard-Identity) without confirming that those headers were listed in the SigV4 SignedHeaders parameter of the Authorization header. Because AWS STS ignores unsigned headers when recomputing and verifying the SigV4 signature, an attacker who captures any valid, fresh SigV4-signed STS GetCallerIdentity request from a victim AWS principal can inject or overwrite the Chainguard-Audience and Chainguard-Identity headers and replay the token to bypass authentication and impersonate the victim identity.

TL;DR

Chainguard Go SDK versions prior to v0.1.107 fail to verify that the Chainguard-Audience and Chainguard-Identity HTTP headers are covered by the AWS SigV4 signature in auth/aws.VerifyToken, allowing an attacker with a captured AWS STS GetCallerIdentity request to inject arbitrary binding headers and bypass authentication.


⚠️ Exploit Status: POC

Technical Details

  • CVE / GHSA ID: CVE-2026-71861 / GHSA-wq26-3j2m-4hvv
  • CWE Classification: CWE-347 (Improper Verification of Cryptographic Signature) / CWE-294 / CWE-290
  • CVSS v3.1 Score: 7.4 High (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N)
  • Affected Component: chainguard.dev/sdk/auth/aws (VerifyToken)
  • Affected Versions: < v0.1.107
  • Patched Version: v0.1.107 (d27997d62aaffe85f905cce4cbe8cdebbd5e24eb)
  • Impact: Authentication Bypass and Federated Identity Impersonation
  • CISA KEV Status: Not Listed

Affected Systems

  • chainguard.dev/sdk (auth/aws package)
  • github.com/chainguard-dev/sdk (auth/aws package)
  • chainguard.dev/sdk (github.com/chainguard-dev/sdk): < 0.1.107 (Fixed in: 0.1.107)

Code Analysis

Commit: d27997d

Enforce SignedHeaders coverage for Chainguard binding headers, reject duplicate headers, pin STS method and host, and validate future-dated timestamps in auth/aws.VerifyToken.

Mitigation Strategies

  • Upgrade chainguard.dev/sdk (github.com/chainguard-dev/sdk) to v0.1.107 or later across all services calling auth/aws.VerifyToken.
  • Enforce cryptographic signature coverage checking on all custom binding headers (chainguard-audience, chainguard-identity, host, x-amz-date) in the SigV4 SignedHeaders parameter.
  • Reject serialized HTTP token requests containing duplicate instances of security-critical headers to prevent HTTP header smuggling between Go's net/http parser and AWS STS.
  • Monitor application logs for ErrUnsignedBindingHeaders, ErrInvalidRequest, and ErrTokenFutureDated errors to detect replay or header injection attempts.

Remediation Steps:

  1. Run go get chainguard.dev/sdk@v0.1.107 and go mod tidy in all Go repositories importing the Chainguard SDK.
  2. Rebuild and redeploy all backend services and authentication endpoints that invoke auth/aws.VerifyToken.
  3. Verify in integration environments that all client token generators include chainguard-audience and chainguard-identity in the SigV4 SignedHeaders field (standard behavior for auth/aws.GenerateToken).
  4. Configure log alerting on the verification error strings introduced in v0.1.107.

References


Read the full report for CVE-2026-71861 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)