Observable Timing Discrepancy in Tink-Java and Tink-Android ChunkedMacVerification
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- None
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-208.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2026-15432
- 2026-10-03 Alias added: GHSA-xxmf-j3rw-f8p2
References
More Google Tink Java vulnerabilities
- TI-2020-07166 Ciphertext integrity weakness in Tink CVSS 3.1MEDIUM 5.3
Sources
- CVE-2026-15432 · CVE Program
- CVE-2026-15432 · NVD
- FIRST EPSS
- GHSA-xxmf-j3rw-f8p2 · 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