Key reuse via overwritten USS-enabled flag
Published Mar 20, 2026 · Updated Mar 20, 2026
Protocol implementation error in Tillitis tkeyclient before 1.3.0 allows physically proximate attackers to derive keys without the supplied USS. In loadApp, copy writes the 32-byte BLAKE2s digest at tx[6], overwriting the use-USS flag at the same index with the digest's first byte. A digest beginning with 0x00 disables USS use, so the resulting CDI and keys match operation without a USS; reaching the flaw requires a connected TKey and a supplied secret.
Summary
What happened
Protocol implementation error in Tillitis tkeyclient before 1.3.0 allows physically proximate attackers to derive keys without the supplied USS. In loadApp, copy writes the 32-byte BLAKE2s digest at tx[6], overwriting the use-USS flag at the same index with the digest's first byte. A digest beginning with 0x00 disables USS use, so the resulting CDI and keys match operation without a USS; reaching the flaw requires a connected TKey and a supplied secret.
The record
- CVE
- CVE-2026-32953
- Published
- Mar 20, 2026
- Updated
- Mar 20, 2026
- Vendor
- Tillitis
- Product
- tkeyclient
- Classifications
- CWE-303
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2026CVE publishedPublication date reported by the CVE source.
- Mar 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.3.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo