Skip to main content
Menu
CVEs

CVE

Chainguard SDK authentication bypass in AWS SigV4 token verification

Only applications using auth/aws.VerifyToken in chainguard.dev/sdk 0.1.106 and earlier are affected. CVSS rates it high (7.4). Fixed in 0.1.107.

CVE-2026-71861Published Updated Summary written by a model

7.4HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.1.107
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.1.107.

Summary

The Chainguard SDK's AWS token verification (auth/aws.VerifyToken) does not require its audience and identity headers to be covered by the AWS request signature. A remote attacker who has not logged in, and who holds a signed AWS identity request from a victim, can change those unsigned headers and replay the request to another relying party, which then accepts the victim's AWS identity for an audience and identity the attacker chose.

Original 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.

Who should check

Teams running Go services that call chainguard.dev/sdk auth/aws.VerifyToken to authenticate AWS workloads, at version 0.1.106 or earlier.

“Only verifiers using auth/aws.VerifyToken are affected.”

github.com

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.4/10CVSS 7.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active
  • Would score about 30 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 0.1.107.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-71861 (Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding headers not required in…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-71861 (entry last updated 2026-11-18):
Affected:
- chainguard-dev sdk: fixed in 0.1.107
Fixed versions: 0.1.107.
Conditions (all must be true for the bug to be hit):
- Application uses auth/aws.VerifyToken to verify AWS-backed tokens (code using only GenerateToken is not affected). (source: https://github.com/chainguard-dev/sdk/security/advisories/GHSA-wq26-3j2m-4hvv)
- Affected chainguard.dev/sdk versions are those up to and including 0.1.106. (source: https://github.com/chainguard-dev/sdk/security/advisories/GHSA-wq26-3j2m-4hvv)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-71861 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71861 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/chainguard-dev/sdk/security/advisories/GHSA-wq26-3j2m-4hvv
- https://github.com/chainguard-dev/sdk/commit/d27997d62aaffe85f905cce4cbe8cdebbd5e24eb
- https://github.com/chainguard-dev/sdk/releases/tag/v0.1.107
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-71861
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-71861"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • chainguard-dev sdk

    fixed in 0.1.107

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · chainguard-dev/sdk · Advisory GHSA-wq26-3j2m-4hvv
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-71861
RecordNVD · CVE-2026-71861
Other links 2
RepositoryGitHub · chainguard-dev/sdk · Commit d27997d6
RepositoryGitHub · chainguard-dev/sdk · Release v0.1.107

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-71861

Is CVE-2026-71861 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The verifier does not require the Chainguard-Audience and Chainguard-Identity binding headers, so a captured AWS GetCallerIdentity proof can be replayed. A relying party may then accept it as the victim's AWS identity for an attacker-chosen audience and identity.Source: github.com

Which versions are affected by CVE-2026-71861?

sdk: before 0.1.107.Source: cve.now feed data

Am I affected, and how do I check?

Affected versions are chainguard.dev/sdk up to and including v0.1.106, and only code that verifies tokens with auth/aws.VerifyToken. Code that uses only GenerateToken is not affected. To check, look at the chainguard.dev/sdk version in go.mod and search the code for calls to auth/aws.VerifyToken.Source: github.com

How do I fix CVE-2026-71861?

Upgrade chainguard.dev/sdk to v0.1.107, the fixed version named in the advisory.Source: github.com

More CVEs