Search
Find a vulnerability
Search criteria
2 vulnerabilities found for sdk by chainguard-dev
CVE-2026-71861 (GCVE-0-2026-71861)
Vulnerability from nvd – Published: 2026-11-18 15:49 – Updated: 2026-11-18 15:49
VLAI
EPSS
VEX
Title
Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders
Summary
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.
Severity
7.4 (High)
CWE
Assigner
References
3 references
| URL | Tags |
|---|---|
| https://github.com/chainguard-dev/sdk/security/ad… | x_refsource_CONFIRM |
| https://github.com/chainguard-dev/sdk/commit/d279… | x_refsource_MISC |
| https://github.com/chainguard-dev/sdk/releases/ta… | x_refsource_MISC |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| chainguard-dev | sdk |
Affected:
< 0.1.107
|
{
"containers": {
"cna": {
"affected": [
{
"product": "sdk",
"vendor": "chainguard-dev",
"versions": [
{
"status": "affected",
"version": "\u003c 0.1.107"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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\u2019s 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."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.4,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-290",
"description": "CWE-290: Authentication Bypass by Spoofing",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-294",
"description": "CWE-294: Authentication Bypass by Capture-replay",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-347",
"description": "CWE-347: Improper Verification of Cryptographic Signature",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T15:49:18.994Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/chainguard-dev/sdk/security/advisories/GHSA-wq26-3j2m-4hvv",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/chainguard-dev/sdk/security/advisories/GHSA-wq26-3j2m-4hvv"
},
{
"name": "https://github.com/chainguard-dev/sdk/commit/d27997d62aaffe85f905cce4cbe8cdebbd5e24eb",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/chainguard-dev/sdk/commit/d27997d62aaffe85f905cce4cbe8cdebbd5e24eb"
},
{
"name": "https://github.com/chainguard-dev/sdk/releases/tag/v0.1.107",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/chainguard-dev/sdk/releases/tag/v0.1.107"
}
],
"source": {
"advisory": "GHSA-wq26-3j2m-4hvv",
"discovery": "UNKNOWN"
},
"title": "Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken \u2014 Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-71861",
"datePublished": "2026-11-18T15:49:18.994Z",
"dateReserved": "2026-08-07T18:26:53.524Z",
"dateUpdated": "2026-11-18T15:49:18.994Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
CVE-2026-71861 (GCVE-0-2026-71861)
Vulnerability from cvelistv5 – Published: 2026-11-18 15:49 – Updated: 2026-11-18 15:49
VLAI
EPSS
VEX
Title
Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders
Summary
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.
Severity
7.4 (High)
CWE
Assigner
References
3 references
| URL | Tags |
|---|---|
| https://github.com/chainguard-dev/sdk/security/ad… | x_refsource_CONFIRM |
| https://github.com/chainguard-dev/sdk/commit/d279… | x_refsource_MISC |
| https://github.com/chainguard-dev/sdk/releases/ta… | x_refsource_MISC |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| chainguard-dev | sdk |
Affected:
< 0.1.107
|
{
"containers": {
"cna": {
"affected": [
{
"product": "sdk",
"vendor": "chainguard-dev",
"versions": [
{
"status": "affected",
"version": "\u003c 0.1.107"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "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\u2019s 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."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 7.4,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-290",
"description": "CWE-290: Authentication Bypass by Spoofing",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-294",
"description": "CWE-294: Authentication Bypass by Capture-replay",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-347",
"description": "CWE-347: Improper Verification of Cryptographic Signature",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-18T15:49:18.994Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/chainguard-dev/sdk/security/advisories/GHSA-wq26-3j2m-4hvv",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/chainguard-dev/sdk/security/advisories/GHSA-wq26-3j2m-4hvv"
},
{
"name": "https://github.com/chainguard-dev/sdk/commit/d27997d62aaffe85f905cce4cbe8cdebbd5e24eb",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/chainguard-dev/sdk/commit/d27997d62aaffe85f905cce4cbe8cdebbd5e24eb"
},
{
"name": "https://github.com/chainguard-dev/sdk/releases/tag/v0.1.107",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/chainguard-dev/sdk/releases/tag/v0.1.107"
}
],
"source": {
"advisory": "GHSA-wq26-3j2m-4hvv",
"discovery": "UNKNOWN"
},
"title": "Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken \u2014 Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-71861",
"datePublished": "2026-11-18T15:49:18.994Z",
"dateReserved": "2026-08-07T18:26:53.524Z",
"dateUpdated": "2026-11-18T15:49:18.994Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}