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.
Scoring
- Severity
- HIGH
- CVSS base score
- 8.2
- CVSS vector
- CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- EPSS probability
- 0.20%
- CWE
- CWE-208
- Published
- 2026-07-21
- Last modified
- 2026-07-24
Affected products
- Google Tink-Java
- Google Tink-Android
Weakness type
Related vulnerabilities
- CVE-2026-87737 — An issue was discovered in the mirage-crypto-ec package before 2.4.0 for OCaml. There is a timing...
- CVE-2026-16037 — Callback Authentication Bypass via Timing Attack in PayTR's PayTR Virtual Pos iFrame API (v9x) WHMCS Module
- CVE-2026-81159 — Commerce CyberSource - Moderately critical - Insufficient input validation - SA-CONTRIB-2026-106
- CVE-2026-84308 — phpseclib — non-constant-time X25519 scalar multiplication permits full private-key recovery
- CVE-2026-82449 — Cockpit CMS before 2.14.1 Account Enumeration via Auth Timing
- CVE-2026-55785 — free5GC AUSF uses non-constant-time authentication comparisons and logs XRES* in 5G-AKA
- CVE-2026-78500 — Dimension Blind SSRF via Database Test Connection Feature
- CVE-2026-80199 — Kimai before 2.54.0 Username Enumeration via Timing Oracle