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.
References
| Link | Resource |
|---|---|
| https://github.com/tink-crypto/tink-java/issues/75 | Patch Vendor Advisory Issue Tracking |
Configurations
History
22 Sep 2026, 13:09
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:google:tink_java:*:*:*:*:*:*:*:* | |
| References | () https://github.com/tink-crypto/tink-java/issues/75 - Patch, Vendor Advisory, Issue Tracking | |
| First Time |
Google tink Java
|
|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 5.9 |
Information
Published : 2026-07-21 17:17
Updated : 2026-09-22 13:09
NVD link : CVE-2026-15432
Mitre link : CVE-2026-15432
CVE.ORG link : CVE-2026-15432
JSON object : View
Products Affected
- tink_java
CWE
CWE-208
Observable Timing Discrepancy
