Research / Finding
fix(crypto): Avoid caching uncacheable nodes in bip32.c
F-TREZOR-BIP32-001
Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.
Read the evidence · View in research browse
Recorded evidence
—score not recorded
fix(crypto): Avoid caching uncacheable nodes in bip32.c
merged
details
- Finding IDs
- F-TREZOR-BIP32-001
- Status
- merged
- Reported via
- security contact
- Note
- public fix commit 26914ff49628 on 2026-02-20. prevents the Stellar derivation path from overflowing the bounded BIP32 cache depth on Trezor One.
F-TREZOR-BIP32-001: Secret handling. Derived secret key material remains in a cache beyond its intended lifetime. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.
Mechanism source for F-TREZOR-BIP32-001
Security area (1seal assessment): Confidentiality. Derived secret key material remains in a cache beyond its intended lifetime. Reviewed 24 Sep 2026.
Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.
How this page groups evidence
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.