Secret recovery via exposed per-card checksum
Published Aug 11, 2026 · Updated Aug 11, 2026
Information disclosure in Ente 2of3 before 2026.07.28 allows local users with one version 1 card to recover guessable secrets offline. The version 1 card serializer writes the secret's byte length and 32-bit FNV-1a checksum in the clear rather than protecting the checksum with the two-card share threshold. Possession of one card is required, and recovery is practical only for low-entropy or predictable secrets that can be tested against those values.
Summary
What happened
Information disclosure in Ente 2of3 before 2026.07.28 allows local users with one version 1 card to recover guessable secrets offline. The version 1 card serializer writes the secret's byte length and 32-bit FNV-1a checksum in the clear rather than protecting the checksum with the two-card share threshold. Possession of one card is required, and recovery is practical only for low-entropy or predictable secrets that can be tested against those values.
The record
- CVE
- CVE-2026-73230
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Ente
- Product
- Ente
- Classifications
- CWE-200
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 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=< 2026.07.28
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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