auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding · Chainguard SDK: AWS SigV4 token replay
Affects chainguard.dev/sdkSource GCVE Database
Not known to be exploited · CVSS 7.4 High : upgrade to 0.1.107 soon.
Data as of 18 Nov 2026, 21:36 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.4 |
|---|
- Patch
- Available – fixed in 0.1.107
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade chainguard.dev/sdk to 0.1.107.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Gochainguard.dev/sdk | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade chainguard.dev/sdk to version 0.1.107 or later, which fixes the vulnerability by requiring the Chainguard-Audience and Chainguard-Identity headers to be included in the SigV4 SignedHeaders before trusting their values. The patch also adds additional checks on the request method, STS host, and timestamp for defense in depth. There is no client-side workaround; operators must update the verifier component promptly.
Description
The chainguard.dev/sdk Go library's auth/aws package has a vulnerability in its VerifyToken function where the Chainguard-Audience and Chainguard-Identity headers are not required to be covered by the AWS SigV4 signature. This allows an attacker to replay a victim's signed AWS STS GetCallerIdentity request for a different audience or identity by modifying these headers after signing, bypassing intended binding protections. The issue affects all versions up to and including v0.1.106 and is fixed in v0.1.107. The fix enforces that these headers must be included in the SigV4 SignedHeaders and adds additional request validations. No client-side workaround exists; upgrading the verifier is required.
References
- github.com/chainguard-dev/sdk/security/advisories/GHSA-wq26-3j2m-4hvv (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-71861 (opens in a new tab)
- github.com/chainguard-dev/sdk/commit/d27997d62aaffe85f905cce4cbe8cdebbd5e24eb (opens in a new tab)
- github.com/chainguard-dev/sdk (opens in a new tab)
- github.com/chainguard-dev/sdk/releases/tag/v0.1.107 (opens in a new tab)