Tink-go 2.8.0 Keyset Validation Bypass via NewHandleWithNoSecrets
Tink-go (tink-crypto/tink-go) through 2.8.0 contains an input-validation vulnerability where keyset.NewHandleWithNoSecrets() and ReadWithNoSecrets() skip the structural Validate() step before constructing a keyset.Handle, allowing malformed public or no-secret keysets that violate Tink's keyset invariants to be accepted. Attackers can supply a malformed keyset, such as one with an enabled public key lacking a valid primary key or a DESTROYED key with no KeyData, causing inconsistent downstream validation where functions like jwt.JWKSetFromPublicKeysetHandle() process the invalid handle and produce a JWK set, potentially misleading applications that rely on successful handle construction as proof of keyset integrity.
CVE-2026-109425
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: cve:CVE-2026-109425
tink-go
Source reference: /containers/cna/affected/0/product
- Affected versions
- Not stated in this record
- Fixed versions
- Not stated in this record
- Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"repo": "https://github.com/tink-crypto/tink-go",
"vendor": "tink-crypto",
"product": "tink-go",
"versions": [
{
"status": "affected",
"version": "2.0.0",
"versionType": "semver",
"lessThanOrEqual": "2.8.0"
}
],
"packageURL": "pkg:github/tink-crypto/tink-go",
"defaultStatus": "unaffected"
}
]- Related CVEs
- CVE-2026-109425
Source reference:
/cveMetadata/cveId
Publisher severity
medium
Source reference: /containers/cna/metrics
- Event
- #22266 · Revision 1
- Added to Heist Feed
- Publisher date