This commit fixes a bug in the COLDCARD hardware wallet firmware that prevented signing of 1-of-1 multisignature transactions. The change also hardens how the wallet detects single-key P2SH-wrapped SegWit inputs so it no longer misclassifi…
PSBT input classification bug fixed1-of-1 multisig signing restoredP2SH-P2WPKH now requires exactly one BIP32 subpath
This is a bugfix for the COLDCARD hardware wallet's NFC sharing feature. Previously, when exporting data over NFC, the device would write the tag contents fresh for each tap/scan attempt. Some phones check the tag multiple times before acc…
NFC export reliability fixRepeated NFC probe handlingNDEF tag state persistence
This commit adjusts color values in the Krux device's user interface themes to improve text and icon contrast. It is purely a visual accessibility/usability fix and does not change any security-sensitive logic, cryptography, input handling…
This commit is a routine internal code reorganization. It moves a helper function that computes a Taproot tweak hash from one module to another and removes an extension trait that was only used to attach that function. There is no security…
A single-word typo in a Trezor hardware-wallet security file meant a safety check did nothing. The code said 'false;' instead of 'return false;', so when a buffer-limit check failed, the function kept running instead of stopping. This coul…
Missing return statement neutralizes a bounds checkSubsequent memcpy may write beyond intended output buffer limitsLocated in secure-element/tropic driver code (core/embed/sec/tropic/tropic.c)
This commit only adds architecture documentation and diagrams to the Trezor firmware repository. There are no code changes, no bug fixes, and no security-related modifications. It is purely a documentation improvement.
This commit is a documentation-only change. It renames and expands an architecture document describing how Trezor firmware is structured, how its security boundaries work, and how third-party apps interact with the system. No code, build s…
Documentation-only change with no executable code modificationsNew document describes existing security architecture, including known limitation that coreapp can request raw secretsNo changes to syscall/smcall verifiers, dispatchers, drivers, or isolation configuration
This is a small code cleanup in Trezor's Python firmware-handling library. It removes an unused firmware header type for Nordic (NRF) chips and renames an internal 'magic' field so it is no longer treated as a user-facing header type. It a…
This commit fixes a small bug in the Python Trezor library that identifies which Trezor hardware model is being used. Previously, the code would crash when it saw a valid but unrecognized model identifier. The fix makes the parser accept a…
No security-relevant keywords in commit title or messageNo changelog entry providedChange is a parsing/validation fix, not a memory-safety or cryptographic fix
This commit fixes a developer tool used to prepare Trezor firmware images. Previously, the tool always signed firmware with internal 'dev keys' regardless of user intent. Now it only signs with dev keys when the user explicitly requests it…
Fixes unintended use of development-only signing keysDeveloper tooling bug, not runtime firmware vulnerabilityNo changelog entry provided by vendor
This commit adds new Python code to the Trezor firmware tools for parsing and building Nordic Semiconductor (nRF) style firmware images. It is a feature addition, not a fix. The code handles firmware headers, TLV metadata blocks, SHA-256 d…
Adds Ed25519 signature verification for nRF firmware imagesAdds SHA-256 digest computation over header + image data + protected TLVAdds integrity checks on TLV table magics, protected TLV size, and trailer
This change only affects Bitcoin Core's internal fuzz testing code. It makes several test mock sockets share a single fake clock instead of each having their own, so timing behaves more realistically during automated fuzz testing. There is…
A quiet fix may be responsible caution—or it may leave users unaware that their assets were ever at risk. CommitWatch preserves the evidence, adds context, and tracks whether vendors disclose, acknowledge, and learn.