Back to security portal
Missing output confirmation in Bitcoin replacement transactions
Reported on May 7, 2026
When signing a replacement (RBF) transaction, the device skipped the standard recipient-confirmation screen for outputs that were not present in the original transaction. A malicious host could therefore include an additional external recipient in the replacement without that address being displayed for approval; the user would only see the resulting amount and fee changes. Replacement transactions can no longer add new recipients at all — the device rejects them outright.
Resolved vulnerabilities
Reported by community. Investigated. Resolved. Because your security is never optional.
- Authenticity proofs not bounded to their secure element on TS7August 16, 2026
- THP pairing could be completed without the pairing codeJune 22, 2026
- Desktop update could install before signature verification completedJune 16, 2026
- Solana account-creation confirmation completenessJune 14, 2026
- Solana signing display improvementJune 12, 2026
- Coordination fee cap shown on CoinJoin authorizationJune 3, 2026