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
1759commits · 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 45 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 candidaterefactor(core): merge passphrase__hidden_wallet into passphrase__walletby Michal Kazda · 7ce6887f · Sep 21, 2026 · 4 filesMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda

refactor(core): merge passphrase__hidden_wallet into passphrase__wallet
[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
access controlauthentication path
AI analysis · Informational 15/100

This commit is a simple user-interface cleanup. It merges two translation labels that both meant 'Passphrase wallet' into a single label, and updates the screens that used the old duplicate label. There is no security-relevant behavior change.

Security candidatefeat(clear_signing): duration formatterby PrisionMike · ec877547 · Sep 21, 2026 · 2 filesMessage 47 · ThinInformational 15Details
Commit message · PrisionMike

feat(clear_signing): duration formatter

- small refactorings
[no changelog]

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This commit adds a new feature to the Trezor Ethereum clear-signing system: a formatter that converts a duration in seconds into a human-readable HH:MM:ss display. It is a straightforward feature addition with no apparent security relevance.

Security candidatechore(core): update UI fixturesby Petr Susil · 247390cb · Sep 18, 2026 · 1 fileMessage 72 · AdequateInformational 11Details
Commit message · Petr Susil

chore(core): update UI fixtures

Multisig accounts are now named on screen, which changes the multisig
signing flows for Bitcoin, Bcash and Zcash.

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
signing boundary
AI analysis · Informational 11/100

This commit only updates the expected screenshots (UI fixtures) used in automated tests. The change reflects that multisig account names are now shown on screen during signing for Bitcoin, Bitcoin Cash and Zcash. There is no code change, no security fix, and no vulnerability present in this commit.

Security candidatechore(clear_signing): add duration formatterby PrisionMike · f072eea9 · Sep 18, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · PrisionMike

chore(clear_signing): add duration formatter

[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 boundary
AI analysis · Informational 15/100

This commit simply adds a new value called FORMATTER_DURATION to an existing list of field formatter types used for Ethereum clear-signing. It only updates generated enum definitions across the codebase and does not change any actual formatting logic, parsing code, or security behavior. There is no indication this introduces a vulnerability.

Security candidatefix(core/bootloader): keep the full block length for block-0 retriesby tychovrahe · dc937ba2 · Sep 18, 2026 · 1 fileMessage 85 · StrongLow 45Details
Commit message · tychovrahe

fix(core/bootloader): keep the full block length for block-0 retries

Block 0 is the only block fetched in two requests: an initial
IMAGE_INIT_CHUNK_SIZE prefetch so the headers can be validated, then the
remainder. `chunk_requested` was serving three roles at once -- request size,
expected buffer fill, and the amount still owed on `remaining` -- and after the
header prefetch it holds only the remainder.

A retry then asked for that remainder from offset 0. The size check compared
`chunk_size` against `chunk_requested + read_offset`, i.e. the remainder against
itself, so it passed and `on_chunk` received a truncated block: the first
`chunk_limit - IMAGE_INIT_CHUNK_SIZE` bytes sitting at buffer offset 0. The hash
then necessarily mismatched, so the retry budget burned down and the upload
aborted. Block-0 retries could never succeed -- on T3W1 that is a 256 KB block,
where a transient BLE error is most likely.

Replace `chunk_requested` with `chunk_expected`: the bytes the buffer must hold
for the chunk to be complete, i.e. the whole block. It is the only field of its
kind left -- every request is derived from it, `remaining` is decremented by what
actually arrived, and `read_offset` goes back to being purely a buffer write
offset. The retry re-fetches the whole block from its start, and the size check
compares against what the buffer must actually hold.

No behavioural change on the success path: the bytes asked for at each request
site are the same as before, and what the old check computed is exactly what
`chunk_expected` now holds.

Alongside, in the same code: the image-size validation becomes an early guard in
`run_image_upload`, which is what guarantees a full init chunk to prefetch;
`confirmed` folds into `headers_parsed`, both having been set at the same point;
and the result dispatch becomes a switch.

The same bug is in wf_firmware_update.c on main; this fix is written against the
extracted engine but applies there unchanged.

[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 validationboot or update path
AI analysis · Low 45/100

This commit fixes a bug in the Trezor bootloader's firmware-update code. When updating firmware, the first block of data is fetched in two pieces: a small initial 'header prefetch,' then the rest. If a communication error happened and the bootloader tried to retry, it accidentally asked for only the leftover remainder but placed it at the start of the buffer. That produced a corrupted block, the hash check failed, every retry failed, and the firmware update aborted. The fix makes retries request the whole first block again from the beginning. There is no evidence this bug was exploitable by an attacker; it appears to be a reliability defect that could brick or stall legitimate updates, especially over Bluetooth on the T3W1 model.

Security candidaterefactor(core/bootloader): separate image upload and image checksby tychovrahe · caab7d9e · Sep 18, 2026 · 4 filesMessage 62 · AdequateInformational 12Details
Commit message · tychovrahe

refactor(core/bootloader): separate image upload and image checks

[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
update trustboot or update path
AI analysis · Informational 12/100

This commit is a code cleanup in the Trezor bootloader. It moves the generic, image-type-agnostic parts of firmware upload (chunk receiving, retry logic, flash erasing/writing, timeouts) into a new reusable module called wf_image_upload.c, while keeping the firmware-specific checks (signatures, versions, user confirmation, per-chunk hash checks) in wf_firmware_update.c. There is no direct evidence in the diff that this change fixes or introduces a security vulnerability; it appears to be a structural refactor to make the upload code reusable for other image types in the future.

Security candidaterefactor(core/eckhart): remove flow_request_numberby obrusvit · aa91d840 · Sep 18, 2026 · 9 filesMessage 77 · AdequateInformational 12Details
Commit message · obrusvit

refactor(core/eckhart): remove flow_request_number

- utilize external menus

[no changelog]

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
boot or update path
AI analysis · Informational 12/100

This is a user-interface code cleanup for the Trezor hardware wallet. It removes a custom multi-page flow for entering a number and replaces it with a simpler, shared number-input screen that uses the device's standard external menu for 'more info' help. There is no indication this change fixes a security bug; it appears to be a normal refactoring to reduce duplicated UI code.

Security candidatechore(core): remove unused trezor_lib/ui featureby cepetr · 1436fbc6 · Sep 18, 2026 · 8 filesMessage 57 · ThinInformational 15Details
Commit message · cepetr

chore(core): remove unused trezor_lib/ui feature

[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
boot or update path
AI analysis · Informational 15/100

This commit removes an unused Rust Cargo feature flag called 'ui' from the Trezor firmware build configuration. It is a cleanup change: the feature was always enabled in practice, so the code now compiles unconditionally. There is no security-relevant change to runtime behavior, no bug fix, and no vulnerability patch.

Security candidatefeat(core): enable Tropic FW updateby Martin Pastyřík · 54e2bfe9 · Sep 18, 2026 · 39 filesMessage 80 · StrongModerate 57Details
Commit message · Martin Pastyřík

feat(core): enable Tropic FW update

Enables update of Tropic firmwares in production. The process starts after unlock to protect the Maintenance bit by PIN.

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
cryptography-sensitive pathboot or update path
AI analysis · Moderate 57/100

This commit adds the ability for the Trezor T3W1 hardware wallet to automatically update the firmware of its Tropic secure chip during normal use. The update is triggered after the user unlocks the device with their PIN, which is intended to prevent unauthorized changes. The change also adds recovery logic so that if an update is interrupted (for example by a power loss), it can be resumed on the next boot. While the feature is security-sensitive, the commit itself is a production enablement patch with safeguards, not an obvious vulnerability.

Security candidatefeat(core): add `alloc` support for Miniscriptby Roman Zeyde · 6ab39e95 · Sep 18, 2026 · 11 filesMessage 80 · StrongInformational 16Details
Commit message · Roman Zeyde

feat(core): add `alloc` support for Miniscript

Use MicroPython tracked allocator (`MICROPY_TRACKED_ALLOC`),
to explicitly deallocate memory (avoid MicroPython GC false positives).

Note: since currently Rust doesn't support fallible allocations,
there is a panic in case of an allocation failure (OOM = RSOD).

[no changelog]

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 16/100

This commit adds a new memory allocator for the Miniscript feature in Trezor firmware. It routes Rust memory allocations through MicroPython's existing 'tracked allocator' so memory can be freed explicitly instead of waiting for garbage collection. The commit message says this avoids 'false positives' from the garbage collector, meaning the old approach could incorrectly report memory as still in use. There is no direct evidence in the commit of a security vulnerability; it reads as a reliability/performance improvement.

Security candidatefix(core/caesar): change confirm middle buttonby obrusvit · e231cc94 · Sep 17, 2026 · 2 filesMessage 57 · ThinLow 27Details
Commit message · obrusvit

fix(core/caesar): change confirm middle button

[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
cryptography-sensitive path
AI analysis · Low 27/100

This commit changes how users confirm an Ethereum authorization screen on Trezor's 'Caesar' layout. Previously, the user had to hold down a button to approve; now a simple tap is enough. The change only affects the user-interface interaction for one specific screen (EIP-7702 authorizations) and updates the corresponding visual test snapshots. There is no direct evidence in the commit that this fixes a security vulnerability, but it could slightly reduce the chance of an accidental or coerced approval if the hold-to-confirm behavior was considered too easy to bypass or too confusing.

Security candidaterefactor(core): merge firmware and unix cargo packagesby cepetr · 6be32440 · Sep 17, 2026 · 25 filesMessage 62 · AdequateInformational 15Details
Commit message · cepetr

refactor(core): merge firmware and unix cargo packages

[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 routine internal cleanup that merges two separate build packages (one for real hardware firmware and one for the desktop emulator) into a single package. It moves source files into subdirectories and updates build scripts accordingly. There is no user-facing change, no bug fix, and no security-relevant behavior change visible in the diff.

Security candidatechore(core): test aes gcm only if enabledby cepetr · 890aca93 · Sep 17, 2026 · 4 filesMessage 67 · AdequateInformational 15Details
Commit message · cepetr

chore(core): test aes gcm only if enabled

[no changelog]

67/100 · AdequateMessage clarity
✓ 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
cryptography-sensitive path
AI analysis · Informational 15/100

This commit is a minor build/test maintenance change. It adds a feature flag (USE_AES_GCM) so that AES-GCM tests are only run when the feature is actually enabled in a particular firmware build. There is no security fix or vulnerability being patched.

Security candidate chore(python, tests): add and update GNU licence headersby M1nd3r · 6dc781c2 · Sep 17, 2026 · 250 filesMessage 95 · StrongInformational 15Details
Commit message · M1nd3r

chore(python, tests): add and update GNU licence headers

- Follow-up to: https://github.com/trezor/trezor-firmware/pull/5471.

[no changelog]

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update pathauthentication path
AI analysis · Informational 15/100

This commit only adds or updates copyright and GNU license header comments in Python test and tooling files. It makes no changes to executable code, so it cannot introduce a security vulnerability or fix one.

Security candidaterefactor(core): move the multisig XPUB title into a translation templateby Michal Kazda · 6d69df16 · Sep 17, 2026 · 11 filesMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda

refactor(core): move the multisig XPUB title into a translation template
[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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a straightforward code cleanup: it moves the on-screen title for multisig XPUB screens from hard-coded English text into the device's translation system. The visible text remains essentially the same, and there is no security change.

Security candidaterefactor(core): render translated strings verbatim in layoutsby Michal Kazda · 162ed3a2 · Sep 17, 2026 · 5 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda

refactor(core): render translated strings verbatim in layouts
- en.json adapted accordingly
[no changelog]

77/100 · AdequateMessage clarity
✓ Specific, 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 15/100

This is a cosmetic code cleanup. It moves punctuation and capitalization out of the Python code and into the translation files so translated strings are shown exactly as written. There is no security-relevant change.

Security candidatefix(python): wait for the device to leave before reconnecting after a rebootby tychovrahe · 6952f4d2 · Sep 17, 2026 · 3 filesMessage 85 · StrongLow 25Details
Commit message · tychovrahe

fix(python): wait for the device to leave before reconnecting after a reboot

After reboot_to_bootloader the pre-reboot device still answers for a moment,
so the reconnect loop could reach a device that is about to reboot and then
fail on the first message. Wait (bounded) for the device to leave before
waiting for it to come back.

Over USB, leaving means it stops enumerating; TrezorConnection.is_present
checks that without opening, since opening would claim the interface and
toggle screen recording.

Over BLE the link can outlive the reboot, and while the main MCU is not
accepting messages the nRF answers everything with Failure(Busy) on its own.
Reusing the link right away therefore got that Busy instead of the bootloader's
Features. There, the device is probed with a v1 Cancel on the same link: no
reply or Busy means it has left, a real reply means it is back.

[no changelog]

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <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 trustboot or update path
AI analysis · Low 25/100

This commit fixes a reliability bug in the Trezor Python library that manages firmware updates. After telling a Trezor device to reboot into bootloader mode, the old code immediately tried to reconnect. Because the pre-reboot device can still respond briefly, or because a Bluetooth link can stay alive while the main processor reboots, the reconnection could grab the wrong device state and fail. The fix waits for the device to truly leave and then come back before continuing. It also adds a timeout to Bluetooth writes so a stuck packet does not hang forever. There is no direct evidence this is a security vulnerability, but a failed or confused update flow could in theory be abused or cause user confusion.

Security candidatechore(core/bolt): remove unneeded `use` statementsby Roman Zeyde · a56f8c3d · Sep 17, 2026 · 2 filesMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore(core/bolt): remove unneeded `use` statements

[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 simply removes two unused Rust import statements (called `use` statements). It does not change any actual code behavior, logic, or security properties of the Trezor firmware.

Security candidatefix(core): add missing colon in Tronby Michal Kazda · 739c2968 · Sep 17, 2026 · 4 filesMessage 57 · ThinInformational 18Details
Commit message · Michal Kazda

fix(core): add missing colon in Tron
[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
cryptography-sensitive pathboot or update path
AI analysis · Informational 18/100

This commit fixes a UI formatting bug in the Tron cryptocurrency flow on Trezor hardware wallets. A missing colon was added to account information labels shown on the device screen. The change is cosmetic and does not appear to affect cryptographic operations, fund safety, or device security.

Security candidatefix(core): combine path/account with labelsby Michal Kazda · c66f6f4d · Sep 17, 2026 · 13 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda

fix(core): combine path/account with labels
[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
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100

This commit is a straightforward user-interface refactoring. It bundles an account/path label together with its corresponding value into a single tuple, instead of passing them as four separate arguments. There is no security-relevant change visible in the code.

Security candidatebuild(core): exclude `FirmwareUI::confirm_fido()` in BTC-only buildsby Roman Zeyde · 93bd25fa · Sep 16, 2026 · 8 filesMessage 62 · AdequateInformational 18Details
Commit message · Roman Zeyde

build(core): exclude `FirmwareUI::confirm_fido()` in BTC-only builds

[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
cryptography-sensitive pathboot or update path
AI analysis · Informational 18/100

This commit is a build cleanup, not a security fix. It makes sure the FIDO (WebAuthn/passwordless login) confirmation screen is only compiled into the universal firmware that supports altcoins and FIDO, and is left out of the smaller Bitcoin-only firmware build. Previously the code was included in all builds but returned a 'not implemented' error on Bitcoin-only devices. The change reduces unused code and build size; it does not patch a vulnerability or change runtime behavior in a security-relevant way.

Security candidatefeat(core): sign messages at an export point under any script typeby Petr Susil · 7c9bfe27 · Sep 16, 2026 · 3 filesMessage 85 · StrongLow 37Details
Commit message · Petr Susil

feat(core): sign messages at an export point under any script type

Signing a message failed unless the host sent the script type matching the
path. Any script type a message can be signed with is now accepted.

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
signing boundarysigning or wallet path
AI analysis · Low 37/100

This commit relaxes a security check in Trezor's Bitcoin message-signing feature. Previously, the device required the host's chosen script type (for example, legacy, SegWit, or native SegWit) to match the exact BIP-32 derivation path. Now, any supported script type is accepted as long as the path reaches a valid 'export point' for one of those script types. The change is described as a feature, not a bug fix, and the tests were rewritten to expect signing to succeed in cases that were previously forbidden or warned. This broadens what a host can ask the device to sign, which could make phishing or UI-bypass attacks slightly easier, but it does not by itself leak keys or allow arbitrary paths.

Security candidatefeat(core): allow signing messages with multisig keysby Petr Susil · d4e4d131 · Sep 16, 2026 · 6 filesMessage 85 · StrongLow 35Details
Commit message · Petr Susil

feat(core): allow signing messages with multisig keys

Signing a message with a BIP-45, BIP-48, Casa or Unchained key failed with a
forbidden key path error. Any path whose public key or address can already be
shown is now accepted.

Fixes issue 7717.

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
signing boundarysigning or wallet path
AI analysis · Low 35/100

This commit fixes a bug where Trezor hardware wallets refused to sign text messages with keys used for multisig wallets (BIP-45, BIP-48, Casa, Unchained). The change makes the device allow message signing on any key path where it can already display a public key or address. It also updates the companion trezorctl tool so that when it auto-detects a multisig-style path, it requests a single-key signature instead. This is a feature/bugfix rather than a vulnerability patch: it widens the set of allowed paths for the SignMessage operation, but only to paths the device already considers safe for public-key/address display.

Security candidatetest: pin the BIP-48 SignMessage permission surfaceby Petr Susil · f6cf5094 · Sep 16, 2026 · 2 filesMessage 95 · StrongInformational 12Details
Commit message · Petr Susil

test: pin the BIP-48 SignMessage permission surface

Add tests covering every BIP-48 path and script type that message signing
accepts or refuses. They record today's behaviour, so later changes show up.

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
signing boundaryaccess controlcredential or privilege statesigning or wallet path
AI analysis · Informational 12/100

This commit only adds new automated tests for the Bitcoin message-signing feature on Trezor hardware wallets. It does not change the firmware's actual signing behavior; it records which BIP-48 derivation paths and script types are currently allowed, warned, or refused. The goal is to make any future behavior changes visible in test results. There is no fix or functional code change here.

Security candidatechore: bump versionsby Roman Zeyde · 18da22f8 · Sep 15, 2026 · 12 filesMessage 63 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore: bump versions

$ tools/bump-version.py core 2.12.6
$ tools/bump-version.py core/embed/projects/secmon 1.0.15
$ tools/bump-version.py core/embed/projects/prodtest 0.3.10
wrote 357 error codes across 25 modules to /home/rzeyde/src/trezor-firmware/core/embed/projects/prodtest/error_codes.json

[no changelog]

63/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100

This commit only updates version numbers and translation metadata. It changes no actual code, logic, or security behavior. There is no security issue here.