Approved changes feed: RSS · Atom
cpe:2.3:a:tink-crypto:tink-go:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Tink Crypto (8d7ae198-834d-52d3-8eb1-6820c4b34475) |
|---|---|
| Product | Tink Go (26ac7f39-11da-54fb-bfce-792dce2a2f0d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-109425 |
vulnerable | 2026-11-03 10:17:39.679521 |
Tink-go 2.8.0 Keyset Validation Bypass via NewHandleWithNoSecrets
MEDIUM (5.3)
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.
Published: 2026-10-12T19:55:37.215Z
Updated: 2026-11-08T14:00:48.625Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.