Bug in multisig verification
Incorrect on-device display/confirmation could have misled users into approving a seemingly minor “fee bump” transaction that was actually malicious, potentially compromising funds in a Bitcoin multisig wallet (threshold > 1). The attacker would need to control one signer, and the other signers’ Trezor Suite would need to be compromised.
In addition to this finding, the researcher submitted several minor reports spanning Firmware, Suite, Connect, and Blockbook. Many of the findings were low severity and focused on robustness and hardening issues such as out-of-bounds reads, parsing/validation bugs, verifier/bypass edge cases, memory-zeroization gaps in cryptography code paths, and transport/protocol handling problems. As these were primarily low-severity or purely informative, they have not been listed here individually. We sincerely thank the researcher for their comprehensive contributions.
Behobene Sicherheitslücken
- Trezor T Bootloader firmware update retry could skip header checks29. September 2026
- E-shop referral discount could be applied to eGift card purchases16. September 2026
- Authenticity proofs not bounded to their secure element on TS716. August 2026
- Monero payment ID could be signed without being shown13. August 2026
- Missing bounds check in JPEG image decoding12. August 2026
- Cardano output datum and reference script not shown in simple transactions11. August 2026