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.
Advisories
Source ID Title
Github GHSA Github GHSA GHSA-wq26-3j2m-4hvv Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Wed, 18 Nov 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Chainguard-dev
Chainguard-dev sdk
Vendors & Products Chainguard-dev
Chainguard-dev sdk

Wed, 18 Nov 2026 16:00:00 +0000

Type Values Removed Values Added
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.
Title Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders
Weaknesses CWE-290
CWE-294
CWE-347
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-18T16:32:30.397Z

Reserved: 2026-08-07T18:26:53.524Z

Link: CVE-2026-71861

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-18T16:18:16.967

Modified: 2026-11-18T17:17:49.390

Link: CVE-2026-71861

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-18T20:42:06Z

Weaknesses