Root cause, affected code and disclosure timeline.
At a glance
Conditions
A malicious host interacting with the signing flow can bypass a reported Merkle preimage integrity check.
What to do
Check for the recorded commit in the app build you use. No fixed app release is recorded here; a code fix is not proof that your device has received it.
1seal reading guide, reviewed 2026-09-25 against the linked records. Not a new vendor assessment or a device rollout check.
Fix / version: commit 0586ab2 Severity: high; numeric score not recorded; CVSS 3.1 vector recorded separately
Source assessments remain separate. Different CVSS versions are not a revision of one another. Code fixes, released versions and deployed updates are distinct evidence.
A reported merkle preimage binding failure bypasses a signing-path integrity gate. This is not a claim about every device or deployed version.
Portfolio updated: 21 Oct 2026 (the last edit of this record set, not a re-check of every upstream source). Status, releases and attribution belong to each source below; none is inferred from another record.
This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.
Paper copy does not update. Current version: 1seal.org/research/findings/F-LEDGER-BTC-MERKLE-001/