Skip to main content
VulnerabilityPublished

CVE-2026-71861: chainguard-dev sdk · Authentication Bypass by Spoofing

Affects chainguard-dev sdkSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 0.1.107 soon.

Data as of 18 Nov 2026, 16:06 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Upgrade chainguard-dev sdk to 0.1.107.

Affected software

ProductAffectedFixed in
chainguard-devsdkAffected
  • <0.1.107
Fixed in
  • 0.1.107

AI-suggested

Upgrade the Chainguard SDK to version 0.1.107 or later, where the vulnerability is fixed. The fix ensures that the Chainguard-Audience and Chainguard-Identity headers are properly covered by AWS SigV4 SignedHeaders, preventing spoofing and replay attacks. No other mitigation is required as the issue is resolved in the official patch.

Description

CVE-2026-71861 is an authentication bypass vulnerability in the Chainguard SDK prior to version 0.1.107. The flaw arises because the auth/aws.VerifyToken function trusts the Chainguard-Audience and Chainguard-Identity headers without ensuring they are covered by AWS SigV4 SignedHeaders. This allows an attacker with a valid signed STS GetCallerIdentity request from a victim to modify these unsigned headers and replay the request to impersonate the victim's AWS identity for an attacker-chosen audience and identity. The issue is fixed in version 0.1.107.

References

Community reviews

Loading reviews…