Skip to content
OpenAdvisories
Medium · 5.3 CVE-2026-109425 EUVD-2026-97823GHSA-5fgm-q74f-6j8f

Tink-go 2.8.0 Keyset Validation Bypass via NewHandleWithNoSecrets

Published Oct 12, 2026 · Updated Nov 8, 2026 · Assigned by VulnCheck

Description

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.

Affected products

VendorProductAffectedFixed
tink-crypto tink-go 2.0.0 – ≤ 2.8.0 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 golang-github-tink-crypto-tink-go 2.9.0-1 —
Debian 13 golang-github-tink-crypto-tink-go No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 golang-github-tink-crypto-tink-go No fix yet —
Ubuntu 26.04 LTS golang-github-tink-crypto-tink-go No fix yet —
ReleasePackageFixed inAdvisory
openSUSE Tumbleweed google-osconfig-agent 20261103.02-1.1 openSUSE-SU-2026:12430-1

Advisories 1

References