Vulnerability in Google Tink-Android
CVE-2026-15432
When verifying a mac with a ChunkedMacVerification object, Tink compares the resulting tag with non constant time comparison. This potentially allows an attacker to use timinig information as a side channel in order to get information how many bytes of a given tag match the correct tag. This in turn could allow to find a correct tag bytewise.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N.
EPSS exploit prediction
EPSS: 0.002 (5.4th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 5th percentile — 5.4% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.002 · newest: 0.002 · change: -0.000
Affected products
- Google Tink-Android — versions All releases before 1.21.0, including 1.21.0.
- Google Tink-Java — versions All releases before 1.21.0, including 1.21.0.
- Google Tink Java
Weakness classification (CWE)
References
- github.com/tink-crypto/tink-java/issues/75 (Patch, Issue Tracking, Vendor Advisory)
Frequently asked questions
- What is CVE-2026-15432?
- CVE-2026-15432 is a medium-severity vulnerability in Google Tink-Android, classified under CWE-208. CVSS score: 5.9/10. Published 2026-07-21.
- How severe is CVE-2026-15432?
- Medium severity. CVSS v3 base score is 5.9 out of 10.