Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Tink's Java package com.google.crypto.tink:tink before 1.5.0 let an attacker alter the key ID bytes of a ciphertext so that a second, different ciphertext decrypts to the same plaintext. The advisory says this matters mainly for deterministic AEAD used with a single key, and that confidentiality and plaintext integrity are not affected. Upgrade to version 1.5.0 or later; the advisory lists no workaround other than applying the fix.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N | CNA (Google) |
- CISA KEV Not listed.
- EPSS 0.0046, the 40th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:20 UTC First seen by agentprime
- 31 Oct 2026, 14:20 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-g5vf-v6wf-7w2r
- OSV: GHSA-g5vf-v6wf-7w2r
- github.com/google/tink/security/advisories/GHSA-g5vf-v6wf-7w2r
- nvd.nist.gov/vuln/detail/CVE-2020-8929
- github.com/google/tink/commit/93d839a5865b9d950dffdc9d0bc99b71280a8899
- github.com/pypa/advisory-database/tree/main/vulns/tink/PYSEC-2020-142.yaml