Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Mon, 12 Oct 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Tink-go 2.8.0 Keyset Validation Bypass via NewHandleWithNoSecrets | |
| Weaknesses | CWE-1286 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-10-12T19:55:37.215Z
Reserved: 2026-10-12T15:52:36.681Z
Link: CVE-2026-109425
No data.
Status : Received
Published: 2026-10-12T20:17:09.293
Modified: 2026-10-12T20:17:09.293
Link: CVE-2026-109425
No data.
OpenCVE Enrichment
Updated: 2026-10-12T22:00:18Z
-
CWE-1286
Improper Validation of Syntactic Correctness of Input