Ciphertext integrity weakness in Tink
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-327.
Summary
A mis-handling of invalid unicode characters in the Java implementation of Tink versions prior to 1.5 allows an attacker to change the ID part of a ciphertext, which result in the creation of a second ciphertext that can decrypt to the same plaintext. This can be a problem with encrypting deterministic AEAD with a single key, and rely on a unique ciphertext-per-plaintext.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Tink | stable to before 1.5 | 1.5 | Patch available | CNA | |
| — | com.google.crypto.tink:tink (Maven) | before 1.5.0 | 1.5.0 | Patch available | GHSA-g5vf-v6wf-7w2r |
- Tink VendorGoogle Affected stable to before 1.5 Fixed in 1.5 Patch available CNA
- com.google.crypto.tink:tink (Maven) Vendor— Affected before 1.5.0 Fixed in 1.5.0 Patch available GHSA-g5vf-v6wf-7w2r
Remediation
- Fix · CNA Tink (Google LLC) Fixed in 1.5
- Fix · GHSA-g5vf-v6wf-7w2r com.google.crypto.tink:tink (Maven) Fixed in 1.5.0 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2020-8929
- 2026-10-03 Alias added: GHSA-g5vf-v6wf-7w2r
References
Patch 2
More Google Tink Java vulnerabilities
- TI-2026-12987 Observable Timing Discrepancy in Tink-Java and Tink-Android ChunkedMacVerification CVSS 4.0HIGH 8.2
Sources
- CVE-2020-8929 · CVE Program
- CVE-2020-8929 · NVD
- FIRST EPSS
- GHSA-g5vf-v6wf-7w2r · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences