TZ
← All projectsTrezor

Trezor firmware

Firmware monorepo for Trezor One, Model T, and Safe devices.

BitcoinHardware walletsNormal
Repository coverage

3768 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

1328security candidates435second-pass queue3191AI analyses
201commits · 30 days
450commits · 60 days
1758commits · 180 days
2832commits · 365 days
Backfill bands
Aug 5 → Feb 61298 seen115 candidatesComplete
Feb 6 → Jun 6775 seen58 candidatesComplete
Jun 6 → Jul 6217 seen13 candidatesComplete
Jul 6 → Aug 5360 seen54 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
841Strong · 80–100
1731Adequate · 60–79
1189Thin · 40–59
7Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
tychovrahe394164355667
Jakub Janků1023067681
Roman Zeyde721230639372
obrusvit333135281364
cepetr301111228259
PrisionMike153101149271
Andrew Kozlik893885267
Petr Susil1159286
Martin Pastyřík291025175
M1nd3r292106248071
Ioan Bizău23076230059
Lukas Bielesch1067592066
Analysis record

Published AI watches

Last scanned 4 minutes ago

Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

ci(core): reuse HW tests Slack webhook

This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.

abfe74f9by Michal Kazda+1−51 file
No security note in commit
Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): name the skipped cases

This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…

98deb5b0by PrisionMike+25−92 files
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): run the cases without display format

This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…

05c1f4efby PrisionMike+63−225 files
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(translations): fix failing tutorial test in FR and small update to PT

This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…

29cbc419by Michal Kazda+19−193 files
No security note in commit
Informational 10 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core/rust): reduce coverage map size

This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…

No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
9bf2fc3aby M1nd3r+1−11 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(translations): sync Crowdin translations

This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…

b2e8b5e6by Thalarion+141−1837 files
No security note in commit
Informational 12 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): edge cases for arrays

This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…

test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
dcdf3068by PrisionMike+169−01 file
No security note in commit
High 70 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): harden task switching against fault injections

This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…

Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
2f159c6bby cepetr+16−51 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(tests): removed unused is_dynamic

This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…

2ada2691by PrisionMike+6−323 files
No security note in commit
Informational 21 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(clear_signing): update proto defs for features to be supported.

This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…

Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
84cb6a4bby PrisionMike+1207−979 files
No security note in commit
Informational 19 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(python): fix protocol_v1 probe for bridge transport

This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…

No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
46492ba4by M1nd3r+18−124 files
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): show language name in change confirm

This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…

5ff5cba0by Michal Kazda+295−67 files
No security note in commit
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(translations): fix failing tests in ES and FR

This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…

9a12ab12by Michal Kazda+15−103 files
No security note in commit
Low 47 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(crypto): hardening against potential side-channel leakage

This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…

Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
7829d7c7by M1nd3r+27−93 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(ci, clear_signing): add clear signing device tests as a nightly run.

This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …

fea125baby PrisionMike+2986−2117 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): move `keccak_32` to unittests

This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…

f3225451by Roman Zeyde+8−122 files
No security note in commit
Informational 15 AI analysisMessage 63 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore: remove SmartCash

This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…

No security-relevant signals detectedPure feature removal / code cleanup
b6d65c00by Roman Zeyde+5−52916 files
No security note in commit
Informational 15 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(common,core,legacy,crypto): remove Groestlcoin

This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…

No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
e22d597dby Roman Zeyde+41−446845 files
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove Tezos

This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …

433075c0by obrusvit+9531−1751964 files
No security note in commit
Informational 24 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(legacy): lower maximum auto-lock delay to 149 hours

This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…

Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
c108f275by Ondřej Vejpustek+16−64 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidatetest(clear_signing): native currency address in token formatterby PrisionMike · c20785e7 · Sep 7, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

test(clear_signing): native currency address in token formatter

[no changelog]

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit only adds a new test case for the Trezor hardware wallet's Ethereum transaction-signing feature. It records a sample Aave 'withdraw ETH' transaction and its expected on-screen snapshots across many languages. There is no change to the actual firmware code that runs on the device, so it cannot introduce a security vulnerability or fix one.

Security candidatefeat(clear_signing): support native currency address in token formatterby PrisionMike · f855babb · Sep 7, 2026 · 1 fileMessage 62 · AdequateInformational 18Details
Commit message · PrisionMike

feat(clear_signing): support native currency address in token formatter

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 18/100

This commit adds support for passing a 'native currency address' into an Ethereum token amount formatter used for Trezor's clear-signing feature. It is a small feature addition with no obvious security bug. There is no evidence in the commit of a vulnerability, exploit, or security fix.

Security candidatechore(clear_signing): support native currency addressesby PrisionMike · eec97d43 · Sep 7, 2026 · 4 filesMessage 62 · AdequateInformational 20Details
Commit message · PrisionMike

chore(clear_signing): support native currency addresses

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 20/100

This commit adds a new optional data field called native_currency_address to the message format used for Trezor's Ethereum clear-signing feature. It only changes protocol definitions and generated serialization code across Python, Rust, and the core firmware. There is no actual logic that uses the new field yet, and the commit is marked as a routine chore with no changelog entry. It does not appear to fix or introduce a security vulnerability on its own.

Security candidatetest(clear_signing): add test fixture for external threshold messageby PrisionMike · 3c4fdb49 · Sep 7, 2026 · 2 filesMessage 95 · StrongInformational 15Details
Commit message · PrisionMike

test(clear_signing): add test fixture for external threshold message

.dat file not added so it would blind sign at the time of merge. We need to update the definitions repo for it. Will be added in a separate PR.
[no changelog]

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit only adds a new test case for the Trezor Ethereum clear-signing feature. It records an expected transaction signature and screen snapshots for an Aave 'repayWithPermit' operation. The actual human-readable definition file needed for clear-signing is intentionally not included, so the test will blind-sign until a separate update is made. There is no change to firmware code, no vulnerability, and no security fix.

Security candidatefeat(clear_signing): add threshold message supportby PrisionMike · b73d87ef · Sep 7, 2026 · 1 fileMessage 62 · AdequateInformational 18Details
Commit message · PrisionMike

feat(clear_signing): add threshold message support

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 18/100

This commit adds a small feature to Trezor's Ethereum 'clear signing' code that lets a data format specify a custom message to show when a token amount exceeds a configured threshold. Previously the device always displayed the word 'unlimited'. There is no obvious security bug in the change itself; it is a user-interface wording feature. The commit does not fix a vulnerability.

Security candidatechore(clear_signing): add threshold message supportby PrisionMike · bc90e0d8 · Sep 7, 2026 · 4 filesMessage 62 · AdequateInformational 15Details
Commit message · PrisionMike

chore(clear_signing): add threshold message support

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 15/100

This commit adds a new optional text field called 'threshold_message' to the data structure used for Ethereum clear-signing. It only updates protocol definitions and generated code in Python, Rust, and the core firmware. There is no change to how data is validated, displayed, or processed. By itself, this commit does not introduce a security vulnerability.

Security candidatefeat(ui): assert property list is never empty.by PrisionMike · fc09afce · Sep 7, 2026 · 6 filesMessage 72 · AdequateInformational 17Details
Commit message · PrisionMike

feat(ui): assert property list is never empty.

Will not affect the production builds.
[no changelog]

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 17/100

This commit adds a runtime check (assert) that ensures a UI function for confirming on-screen properties is never called with an empty list. It also changes the expected input type from a generic iterable to a sequence and converts a couple of generator expressions into lists. The commit message explicitly says it will not affect production builds, because assertions are typically stripped from production firmware. There is no direct evidence this fixes an active security bug; it appears to be a defensive hardening measure for development/debug builds.

Security candidatefix(core/xtask): pad a combined image's erased regions as erasedby tychovrahe · 7d423838 · Sep 7, 2026 · 2 filesMessage 95 · StrongLow 25Details
Commit message · tychovrahe

fix(core/xtask): pad a combined image's erased regions as erased

A combined image pads the gaps between its sections with 0x00. That is
wrong for any region the boot chain ERASES on first boot: the bootloader
erases the UCB (`boot_ucb_erase`), so the device stops matching the
image it was flashed from the moment it boots, and a factory line that
verifies by reading flash back would fail.

Pad that region with 0xFF, the erased state, and the erase becomes a
no-op -- it checks `flash_area_is_erased` and skips -- leaving the image
byte-identical to what is on the device. The rule generalises: a region
the boot chain erases has to be combined in its erased state.

The region is located from the model's memory.ld, so a model without one
is untouched; both cases are covered by tests.

[no changelog]

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trust
AI analysis · Low 25/100

This commit fixes a build-time tooling bug in Trezor's firmware build helper. When creating a combined firmware image, the tool was filling unused gaps between sections with 0x00 bytes. One specific gap (the UCB region) is erased by the bootloader on first boot. Because erased flash reads as 0xFF, the device would no longer match the original image after its first boot, causing factory verification to fail. The fix makes the tool fill that gap with 0xFF instead, so the image stays identical after the device boots. This is a manufacturing/verification bug, not a security vulnerability that can be exploited by an attacker.

Security candidatechore(core): disable BIP39 cacheby M1nd3r · 59199f20 · Sep 7, 2026 · 1 fileMessage 57 · ThinLow 46Details
Commit message · M1nd3r

chore(core): disable BIP39 cache

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Low 46/100

This commit turns off an internal performance cache for BIP39, the system that converts a recovery seed phrase into cryptographic keys on Trezor hardware wallets. Disabling a cache is usually a defensive change: it can prevent sensitive seed-derived data from lingering in device memory longer than necessary. However, the commit gives no explanation, changelog entry, or linked security report, so we cannot tell whether this fixes a known vulnerability or is just a precautionary hardening measure.

Security candidatefix(core/bootloader): report the actual error from a failed wipe stepby tychovrahe · 0a0d00aa · Sep 7, 2026 · 1 fileMessage 85 · StrongInformational 20Details
Commit message · tychovrahe

fix(core/bootloader): report the actual error from a failed wipe step

`send_error_conditionally` ignored its `msg` argument and always sent
"Could not read BLE status", so a host watching a WipeDevice was told the
wrong thing whenever anything but the BLE status read failed -- an
inability to issue a BLE command, to erase bonds, or to erase flash.

[no changelog]

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 20/100

This is a minor bug fix in the Trezor bootloader. When wiping the device, if a step failed, the bootloader always reported the same generic error message ('Could not read BLE status') even when the actual failure was something else, such as failing to erase stored data or issue a Bluetooth command. The fix makes the bootloader report the correct, specific error message. It does not change whether errors happen or how they are handled; it only corrects the message sent to the host computer.

Security candidaterefactor(core/rust): tweak MenuIntent's micropython dependencyby matejcik · 617e0383 · Sep 7, 2026 · 3 filesMessage 62 · AdequateInformational 12Details
Commit message · matejcik

refactor(core/rust): tweak MenuIntent's micropython dependency

and fix Error usage

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 12/100

This is a small internal code cleanup in the Trezor firmware's Rust UI layer. It moves some MicroPython-specific code into its own submodule and removes an unused import. There is no visible change to user-facing behavior or security-sensitive logic.

Security candidatefeat(clear signing): show signing context on all flowsby PrisionMike · da463970 · Sep 7, 2026 · 7 filesMessage 62 · AdequateInformational 17Details
Commit message · PrisionMike

feat(clear signing): show signing context on all flows

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundarycryptography-sensitive pathsigning or wallet path
AI analysis · Informational 17/100

This commit changes how Trezor hardware wallets display Ethereum transaction details on screen during 'clear signing' flows. It adds more context—such as the contract address, account name, and derivation path—to the confirmation screens across all supported device models (Bolt, Caesar, Delizia, Eckhart). The change is purely user-interface related and does not alter transaction validation, cryptography, or how funds are moved.

Security candidatetest(clear_signing): benqi claim empty property listby PrisionMike · fb8a6ddd · Sep 7, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

test(clear_signing): benqi claim empty property list

[no changelog]

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit only adds a new test case for the Benqi sAVAX redeem function. It includes test data, a small external definition file, and expected screen hashes for automated UI tests. There is no change to production firmware code, no bug fix, and no security patch.

Security candidatetest(clear_signing): benqi claim empty property listby PrisionMike · 1b355134 · Sep 7, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

test(clear_signing): benqi claim empty property list

[no changelog]

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 15/100

This commit only updates a single test data file used for Ethereum clear-signing tests. The title says it is adjusting a Benqi claim test case to use an empty property list. There is no code change, no firmware change, and no indication of a security fix or vulnerability.

Security candidatefix(clear_signing): skip empty property screenby PrisionMike · c7473b71 · Sep 7, 2026 · 4 filesMessage 57 · ThinInformational 19Details
Commit message · PrisionMike

fix(clear_signing): skip empty property screen

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundarycryptography-sensitive path
AI analysis · Informational 19/100

This commit is a minor user-interface fix for Ethereum 'clear signing' flows on Trezor hardware wallets. It simply skips showing a contract-details screen when there are no details to display. There is no indication this is a security fix, and the change does not alter what users must approve before signing a transaction.

Security candidatechore(core/rust): remove unused `heapless::String` importby Roman Zeyde · 8acd6151 · Sep 7, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · Roman Zeyde

chore(core/rust): remove unused `heapless::String` import

Should have been done in #7796.

[no changelog]

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update pathauthentication path
AI analysis · Informational 15/100

This commit removes an unused import of a string type from a Rust source file. It is a routine code cleanup with no functional change and no security relevance.

Security candidatefeat(trezorlib): improve terse firmware header outputby cepetr · ace402bd · Sep 4, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · cepetr

feat(trezorlib): improve terse firmware header output

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100

This commit is a minor user-interface improvement for a developer/debugging tool. It adds a 'verbose' mode to the text output shown when inspecting a Trezor firmware file header. In non-verbose mode it now prints a shorter summary (device model, version, fingerprint, signature/hash status) instead of dumping every header field. There is no change to security checks, cryptography, firmware loading, or device behavior.

Security candidatefeat(core/xtask): let flash take an explicit binaryby tychovrahe · ae4272d1 · Sep 4, 2026 · 2 filesMessage 95 · StrongInformational 19Details
Commit message · tychovrahe

feat(core/xtask): let flash take an explicit binary

`flash` could only act on the artifact the current tree just built, so a
prebuilt or archived image had no path in -- e.g. a bootloader captured from
another branch, or one kept alongside a test fixture.

`-f/--file` replaces WHAT is written, never WHERE: the destination address
still comes from the project plus the model's memory.ld, so a prebuilt binary
lands exactly where that project belongs and cannot drift from the linker
layout.

[no changelog]

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
update trust
AI analysis · Informational 19/100

This commit adds a `-f/--file` option to Trezor's internal `flash` developer tool so engineers can flash a prebuilt firmware or bootloader file instead of only the binary produced by the current source tree. The same commit also fixes a command-injection risk in the OpenOCD flashing script by properly quoting file paths that contain spaces or special characters. The change is a developer convenience plus a hardening fix; it does not affect end-user device security directly.

Security candidatebuild: fix builds on MacOS / clang / newer gccby matejcik · ed9a3e31 · Sep 4, 2026 · 6 filesMessage 80 · StrongInformational 18Details
Commit message · matejcik

build: fix builds on MacOS / clang / newer gcc

* Mach-O dislikes section ".buf"
* projects should use local version.h and not rely on it magically being
the only version.h in include path
* g_lt_log_cli is set but not read
* "TRZC" is a 5-byte string which you aren't supposed to stuff into a
4-byte array

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · Informational 18/100

This commit fixes several build-compatibility problems in the Trezor firmware so it compiles on MacOS, clang, and newer gcc. The changes include using the correct local header file, avoiding a special memory section name that MacOS object files reject, silencing a compiler warning about an unused log variable in emulator builds, and fixing a 5-character string being squeezed into a 4-character space. These are primarily build/robustness fixes rather than patches for an active security vulnerability.

Security candidatefeat(core): add a boot command that enters the bootloader ready to talkby tychovrahe · d1330f9e · Sep 4, 2026 · 13 filesMessage 85 · StrongLow 27Details
Commit message · tychovrahe

feat(core): add a boot command that enters the bootloader ready to talk

BOOT_COMMAND_STOP_AND_WAIT lands on the bootloader's intro screen -- "Go to
bootloader menu" per the BootCommand protobuf, which is deliberate. But only
the wait-for-host screen calls workflow_ifaces_init(), so on the intro screen
the wire interfaces are not up: a host that just rebooted the device cannot
talk to it until somebody taps through.

BOOT_COMMAND_STOP_AND_CONNECT is the same stop, entered on the connect
screen instead. The whole behavioural difference is which screen the workflow
starts on:

screen_t screen = connect_to_host ? SCREEN_WAIT_FOR_HOST : SCREEN_INTRO;

It authorizes nothing -- no consent material, no effect on any validity gate
-- which is what makes it safe to hand to firmware, unlike CONTINUE_UPGRADE
(deliberately bridge-less so firmware cannot reach the weaker boot gate).
reboot_and_connect() therefore gets the usual syscall AND smcall bridges,
since firmware runs unprivileged.

The motivating case is a caller that has just invalidated its own firmware
and knows a host is waiting: the intro screen would strand the device behind a
tap it has no way to ask for. Not exposed over the wire yet; a host-initiated
RebootToBootloader still lands on the menu, which a later protobuf addition
could fix.

[no changelog]

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustdefensive validationcredential or privilege stateboot or update path
AI analysis · Low 27/100

This commit adds a new internal reboot path that lets the Trezor Core firmware restart the device into the bootloader and immediately activate the USB/wire connection, skipping the usual intro screen that normally requires a finger tap. The change is intentionally limited: it does not approve any firmware installation, downgrade, or other security-sensitive action; it only changes which screen the bootloader shows first. It is exposed to unprivileged firmware through both a normal system call and a secure-monitor call, but it is not yet reachable from a host computer over USB. The main security consideration is that it slightly enlarges the attack surface for reboot-based attacks, though the commit message and code comments explicitly describe it as authorization-free and safe compared to the existing auto-upgrade reboot command.

Security candidatechore: remove deadcode from `pyright_tool.py`by obrusvit · ac25643b · Sep 3, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit

chore: remove deadcode from `pyright_tool.py`

- features removed are not used anywhere

[no changelog]

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
seed or entropy path
AI analysis · Informational 15/100

This commit is a routine cleanup of an internal Python linting helper script. It removes unused features from `pyright_tool.py` (a tool that manages type-checker suppressions) and updates two comments in unrelated firmware source files to match a new alias format. There is no change to the actual Trezor firmware code that runs on devices, no security fix, and no vulnerability.

Security candidaterefactor(core): simplify Bitcoin signer machineryby matejcik · a8e53a73 · Sep 3, 2026 · 17 filesMessage 80 · StrongInformational 12Details
Commit message · matejcik

refactor(core): simplify Bitcoin signer machinery

This commit does not touch the bitcoin signing _algorithm_, merely the
_harness_ that runs it.

It takes advantage of global `context` availability to directly await
layout and wire call functions instead of traversing through a
tedious-to-maintain sequence of UI wrapper objects and a custom local
event loop.

Makes the signing harness more readily understandable and significantly
reduces amount of boilerplate.

[no changelog]

Co-Authored-By: Roman Zeyde <roman.zeyde@satoshilabs.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 12/100

This is a code cleanup (refactor) of the Bitcoin signing workflow inside Trezor firmware. It replaces a custom hand-rolled event loop and a pile of UI wrapper objects with ordinary async/await calls. The commit message and diff show no change to the actual signing algorithm or security checks; it only rewrites the surrounding machinery to make the code easier to maintain. Tests were updated to match the new calling style.

Security candidatechore(core): save 15KB of flash by eliminating source filenamesby cepetr · 8eb27f83 · Sep 3, 2026 · 2 filesMessage 62 · AdequateInformational 11Details
Commit message · cepetr

chore(core): save 15KB of flash by eliminating source filenames

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 11/100

This commit is a routine size-optimization change for the Trezor firmware. It removes source filenames from compiled code to save 15KB of flash storage and rearranges linker sections. There is no indication this is a security fix or introduces a vulnerability.

Security candidatechore(tests): use named parametersby M1nd3r · 54a213d7 · Sep 3, 2026 · 18 filesMessage 82 · StrongInformational 15Details
Commit message · M1nd3r

chore(tests): use named parameters

[no changelog]

Co-Authored-By: Claude Opus 5 (1M) <noreply@anthropic.com>

82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathauthentication path
AI analysis · Informational 15/100

This commit only rewrites test code to use named pytest parameters (adding readable IDs to test cases). It does not change any production firmware, wallet logic, or security behavior. There is no security issue here.

Security candidatefix(core/bootloader): mark check_vendor_header_lock warn-unused-resultby tychovrahe · f58e7e79 · Sep 3, 2026 · 2 filesMessage 90 · StrongLow 25Details
Commit message · tychovrahe

fix(core/bootloader): mark check_vendor_header_lock warn-unused-result

The three sibling checks in sec/image.h -- check_vendor_header_model, _sig
and _keys -- are all declared `secbool __wur (const vendor_header *const)`.
This one predates them in that respect and had neither the attribute nor the
second const, even though dropping its result would silently skip an
authorization check rather than fail.

No call site changes: both existing callers already consume the value (one
assigns it, one wraps it in ensure()).

[no changelog]

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

90/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
access controlupdate trustboot or update path
AI analysis · Low 25/100

This is a small hardening change to the Trezor bootloader. It adds a compiler warning attribute to a security check function so that future programmers cannot accidentally call it and ignore its pass/fail result. The current code already uses the result correctly at both call sites, so there is no active bug being fixed—only prevention of a future mistake.