Improper Validation of Syntactic Correctness of Input Affecting golang-github-tink-crypto-tink-go package, versions *


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.19% (9th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-GOLANGGITHUBTINKCRYPTOTINKGO-20936433
  • published14 Oct 2026
  • disclosed12 Oct 2026

Introduced: 12 Oct 2026

NewCVE-2026-109425  (opens in a new tab)
CWE-1286  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest golang-github-tink-crypto-tink-go.

NVD Description

Note: Versions mentioned in the description apply only to the upstream golang-github-tink-crypto-tink-go package and not the golang-github-tink-crypto-tink-go package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

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 Base Scores

version 3.1