tink-crypto tink-go up to 2.8.0 Keyset keyset.NewHandleWithNoSecrets/ReadWithNoSecrets input validation

Summaryinfo

A vulnerability has been found in tink-crypto tink-go up to 2.8.0 and classified as problematic. This impacts the function keyset.NewHandleWithNoSecrets/ReadWithNoSecrets of the component Keyset. This manipulation causes input validation. This vulnerability is tracked as CVE-2026-109425. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in tink-crypto tink-go up to 2.8.0 and classified as problematic. Affected by this vulnerability is the function keyset.NewHandleWithNoSecrets/ReadWithNoSecrets of the component Keyset. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect integrity. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-109425 since 10/12/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/12/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• tink-crypto

Name

• tink-go

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4
• 2.5
• 2.6
• 2.7
• 2.8.0

Website

• Product: https://github.com/tink-crypto/tink-go/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion