CVE-2026-109425
Received Received - Intake

Input Validation Flaw in Tink-go Crypto Library

Publication date: 2026-10-12

Last updated on: 2026-10-12

Assigner: 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-12
Last Modified
2026-10-12
Generated
2026-10-13
AI Q&A
2026-10-12
EPSS Evaluated
N/A
NVD
CVE-2026-109425
EUVD
EUVD-2026-97823

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
tink-crypto tink-go 2.0.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-1286 The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-109425 is an input-validation flaw in Tink-go's keyset.NewHandleWithNoSecrets() and ReadWithNoSecrets() functions. These functions skip structural validation before creating a keyset.Handle, allowing malformed keysets like public keys without valid primary keys or DESTROYED keys without KeyData to be accepted. This bypasses Tink's normal keyset invariants.

Detection Guidance

To detect this vulnerability, check if your system uses Tink-go versions 2.0.0 through 2.8.0. Run: go list -m github.com/tink-crypto/tink-go@v* to verify the installed version. Inspect code using keyset.NewHandleWithNoSecrets() or ReadWithNoSecrets() for missing structural validation calls.

Impact Analysis

Attackers could exploit this to supply invalid keysets to applications using Tink-go. While most APIs reject malformed handles, functions like jwt.JWKSetFromPublicKeysetHandle() may process them, creating inconsistent validation. Applications relying on successful handle construction as proof of integrity could be misled.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR or HIPAA as it is a structural validation issue in cryptographic key handling. However, it could indirectly impact compliance if applications rely on the vulnerable functions to validate keysets for encryption or authentication, potentially leading to unauthorized data access or integrity issues.

Mitigation Strategies

Upgrade Tink-go to the latest version beyond 2.8.0 where the validation issue is fixed. Review and update code using NewHandleWithNoSecrets() or ReadWithNoSecrets() to ensure proper validation is performed before handle construction.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-109425. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart