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
1762commits · 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 56 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 candidatechore(python): add root debug keys for T3W1 authenticationby M1nd3r · f9f28143 · Oct 27, 2026 · 1 fileMessage 67 · AdequateInformational 18Details
Commit message · M1nd3r

chore(python): add root debug keys for T3W1 authentication

[no changelog]

67/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Informational 18/100

This commit adds two extra public debug root keys (Ed25519 and ML-DSA-44) to the Python trezorlib library so it can authenticate the upcoming T3W1 hardware variant during development. Debug keys are already public, non-production trust anchors; adding more of them is a routine key-list update and does not by itself create a vulnerability.

Security candidaterefactor(python): use ML-DSA-44 OID from cryptographyby M1nd3r · 2f97f951 · Oct 27, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · M1nd3r

refactor(python): use ML-DSA-44 OID from cryptography

- `SignatureAlgorithmOID.ML_DSA_44` is available since cryptography v49.0.0, introduced in https://github.com/pyca/cryptography/pull/14884.

[no changelog]

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundaryauthentication path
AI analysis · Informational 15/100

This is a minor code cleanup in the Python Trezor library. It replaces a hard-coded identifier for the ML-DSA-44 signature algorithm with the official constant provided by the cryptography library. There is no security bug being fixed and no change in behavior for users.

Security candidatefix(core): flash F4 firmware parts to their own addressesby tychovrahe · 5718d0aa · Oct 27, 2026 · 5 filesMessage 85 · StrongModerate 57Details
Commit message · tychovrahe

fix(core): flash F4 firmware parts to their own addresses

- split the F4 firmware upload image into part 1 and part 2 when
flashing or combining, part 2 belongs at FIRMWARE_P2_START
- writing it in one piece put part 2 over the secret sector
- fix the misleading split_pad_to comment

[no changelog]

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

This commit fixes a bug in Trezor's internal firmware flashing tools. Previously, when flashing or combining firmware for STM32F4-based devices, the second half of the firmware image was written to the wrong flash address (0x08100000) and could overwrite the 'secret sector'—a protected area that holds sensitive device secrets. The fix splits the firmware image into two parts and writes part 2 to its correct address (0x08120000). The bug is in developer/flash tooling, not in the device firmware itself, so ordinary users are not directly affected unless they use these internal tools.

Security candidatefix(core/bolt): paginate dialogsby obrusvit · 477d4a76 · Oct 27, 2026 · 7 filesMessage 57 · ThinLow 27Details
Commit message · obrusvit

fix(core/bolt): paginate dialogs

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

This commit fixes how long text is shown on Trezor Safe 3 and similar devices using the 'Bolt' user interface. Previously, long messages in confirmation dialogs could be cut off or not fully visible. Now these dialogs can paginate (split across multiple swipeable pages) so users can read the entire content before approving. The change is a UI/UX improvement rather than a direct exploit fix, but truncated security warnings could theoretically lead users to confirm something they did not fully see.

Security candidatefix(core/bolt): Marquee for PIN promptby obrusvit · 5b2b65d5 · Oct 27, 2026 · 2 filesMessage 57 · ThinInformational 20Details
Commit message · obrusvit

fix(core/bolt): Marquee for PIN prompt

[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
access controlauthentication path
AI analysis · Informational 20/100

This commit changes the PIN entry screen so that long prompt text scrolls smoothly like a marquee instead of being crammed or clipped. It is a user-interface polish fix with no apparent security relevance.

Security candidatefix(core): give USB EP0 receptions a full-packet bufferby tychovrahe · 0b9ac86f · Oct 27, 2026 · 7 filesMessage 85 · StrongHigh 77Details
Commit message · tychovrahe

fix(core): give USB EP0 receptions a full-packet buffer

- the OTG core accepts a full packet on EP0 OUT however short the armed
length; the stack armed the status stage with a NULL buffer and VCP
received class requests into an 8-byte one, so a host could make the
HAL write through NULL or past the VCP buffer
- receive all of them into a packet-sized buffer in the device handle

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
boot or update path
AI analysis · High 77/100

This commit fixes a USB memory-safety bug in Trezor hardware wallets. When the device expected no data during the final 'status' handshake of a USB control transfer, it told the USB hardware to write incoming bytes to address zero (NULL) or into an 8-byte command buffer. The USB hardware can actually deliver a full 64-byte packet regardless of what length was requested, so a malicious or misbehaving USB host could make the device write memory past the intended location or through the NULL pointer, causing a crash or potentially worse. The fix gives every such reception a dedicated 64-byte buffer inside the device handle.

Security candidatefeat(tests,clear_signing): update definition fixtures from devby PrisionMike · 906d0092 · Oct 27, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

feat(tests,clear_signing): update definition fixtures from dev

[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 updates an internal helper script used to refresh test data for Ethereum 'clear signing' definitions. It adds an optional --dev mode so developers can fetch unsigned development definitions from an internal-only server and verify them with development keys. There is no change to the firmware that runs on customer devices, no change to production signature verification, and no disclosed security issue.

Security candidaterefactor(core): rename feature noise to noise_kk1by Martin Milata · 32d898c2 · Oct 26, 2026 · 3 filesMessage 57 · ThinInformational 15Details
Commit message · Martin Milata

refactor(core): rename feature noise to noise_kk1

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

This commit is a simple internal rename of a Rust build feature from 'noise' to 'noise_kk1' and removes one unused source file ('noise_xxpsk3.c') from the build. There is no change to how the device works, no bug fix, and no security-relevant behavior change visible in the diff.

Security candidatefix(core/bootloader): initialize BLE once on the wipe path [no changelog]by tychovrahe · e59fe6ac · Oct 26, 2026 · 2 filesMessage 85 · StrongInformational 18Details
Commit message · tychovrahe

fix(core/bootloader): initialize BLE once on the wipe path [no changelog]

drivers_init() already brought the driver up; the wipe branch called
ble_init() a second time. The STM32 driver ignores a repeated init, the
unix one re-registered its handles and failed, so a wipe boot command
ended on the failure screen in the emulator. Drop the second call and
give the unix driver the same already-initialized guard.

Co-Authored-By: Claude Fable 5.1 <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 · Informational 18/100

This is a small bug fix in the Trezor bootloader's wipe feature. When wiping the device, the code was accidentally initializing the Bluetooth (BLE) system twice. On real hardware the second call was ignored, but in the software emulator it caused the wipe process to end on an error screen. The patch removes the redundant second initialization and also makes the emulator's BLE driver ignore repeated initializations, matching the real hardware behavior. It does not appear to be a security vulnerability.

Security candidatefeat(core,legacy): restrict xpub exportby Petr Susil · f5184bdd · Oct 26, 2026 · 27 filesMessage 80 · StrongLow 46Details
Commit message · Petr Susil

feat(core,legacy): restrict xpub export

Quantum computers may break exported xpubs. Warn before exporting xpubs
shallower than 2 levels (except known third-party paths) and of SLIP-15,
SLIP-16 and BIP-85.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
(cherry picked from commit 0b594247cd3342949b4888bb1f4e89dc641f8384)

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 pathsigning or wallet pathboot or update path
AI analysis · Low 46/100

This commit adds a warning to Trezor devices when a user tries to export an extended public key (xpub) from a path that is considered risky in a future quantum-computing scenario. It does not block the export, but it makes the user confirm they understand the risk. The affected paths are very shallow ones (less than two derivation levels) and paths used for encryption keys or derived passwords (SLIP-15, SLIP-16, BIP-85). Some well-known third-party uses of shallow paths are allowed without a warning. This is a hardening change, not a fix for an active bug or exploit.

Security candidatefix(cardano): implement cip-129 for drep credentialsby PrisionMike · ff3d5c50 · Oct 25, 2026 · 5 filesMessage 85 · StrongModerate 59Details
Commit message · PrisionMike

fix(cardano): implement cip-129 for drep credentials

Fixes Cardano staking: Custom DRep address may not match the address shown on the device
Fixes #6192

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
credential or privilege state
AI analysis · Moderate 59/100

This update fixes how Trezor displays Cardano DRep (delegated representative) addresses on the device screen. Previously, the device used an older bech32 format that could show a different address than what the user expected, potentially leading them to delegate voting power to the wrong representative. The fix adopts the newer CIP-129 standard so the displayed address matches the one used on the blockchain.

Security candidatefix(core/caesar): hold to confirm firmware updateby obrusvit · a95d9b94 · Oct 25, 2026 · 1 fileMessage 80 · StrongLow 28Details
Commit message · obrusvit

fix(core/caesar): hold to confirm firmware update

- The screen before rebooting to the bootloader was confirmed by a
single
right press since the new menu navigation, base used both buttons.
- Pressing both buttons would clash with "Shift", so it is a hold.

[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
update trustcryptography-sensitive pathboot or update path
AI analysis · Low 28/100

This commit changes how a user confirms a firmware update on the Trezor Safe 3 (Caesar layout). Previously, pressing the right button once could confirm the update; now the user must hold a button for a short period. The change prevents accidental or malicious confirmations when the right-button press is part of a different navigation gesture, and it avoids conflict with the new 'Shift' action that uses both buttons.

Security candidatefeat(clear_signing): AddressName formatter updatedby PrisionMike · 1549d35b · Oct 24, 2026 · 5 filesMessage 77 · AdequateLow 26Details
Commit message · PrisionMike

feat(clear_signing): AddressName formatter updated

- When types in (contract,token) we request host for a clear name for the contract.
[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
signing boundarysigning or wallet path
AI analysis · Low 26/100

This commit adds a new optional feature to Trezor's Ethereum clear-signing system. When a transaction field is marked as an address name and its type is 'contract' or 'token', the device can now ask the connected computer (host) to look up a friendly name for that address. If the host provides a name, the device shows that name to the user instead of the raw address. The change is a feature addition, not a direct fix for a known security bug, but it touches the code that decides what text users see on their device screen during transaction approval.

Security candidatefix(crypto): copy only the digest length in `blake2s_Final()`by Ondřej Vejpustek · dd810b46 · Oct 23, 2026 · 2 filesMessage 85 · StrongModerate 60Details
Commit message · Ondřej Vejpustek

fix(crypto): copy only the digest length in `blake2s_Final()`

`blake2s_Final()` copied `outlen` (the caller's buffer size) bytes from
the 32-byte internal buffer, so `outlen > 32` caused an out-of-bounds
stack read. Copy `S->outlen` instead, same as `blake2b_Final()`.

Inherited probably from upstream commit 932be4e, which forgot to update
the `memcpy()` in `ref/blake2s-ref.c`.

[no changelog]

(cherry picked from commit b109a5bb745f1843dfd40790fe46903c66d9564e)

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
cryptography-sensitive path
AI analysis · Moderate 60/100

This commit fixes a memory safety bug in the Trezor firmware's implementation of the BLAKE2s hashing function. The finalization routine was copying as many bytes as the caller's output buffer could hold, rather than the actual hash digest length. If a caller passed a buffer larger than 32 bytes, the function would read past the end of its internal 32-byte buffer, potentially leaking nearby stack data into the output. The fix makes BLAKE2s behave consistently with the already-correct BLAKE2b implementation.

Security candidatefix(legacy): forbid removed Unchained pathby Alejandro Pacheco · 2a320bfa · Oct 23, 2026 · 4 filesMessage 80 · StrongModerate 64Details
Commit message · Alejandro Pacheco

fix(legacy): forbid removed Unchained path

- 82da663a86 removed the deprecated Unchained Capital pattern
`m/45'/coin_type'/account'/[0-1000000]/address_index`, but left the
five-element `m/45'` arm of `coin_path_check()` with no rejection for
a hardened `address_n[1]`. Such a path matches no pattern, yet it was
accepted as valid.
- With safety checks `Strict`, `GetAddress` showed the multisig address
of such a path (any account or address index, also a Bitcoin path on
Testnet) and `SignTx` signed a Bitcoin-path multisig input on Litecoin.
With `PromptTemporarily`, neither showed the unknown path warning.
- Reject it, as the other arms of coin_path_check() reject an unknown
pattern and as core does.

(cherry picked from commit ab9fd8af1ea8335a0270377891957dc56104b4d8)

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
defensive validationcryptography-sensitive pathsigning or wallet pathboot or update path
AI analysis · Moderate 64/100

This commit fixes a bug in the Trezor Model One (legacy) firmware where an old, removed multisig key path pattern was still being accepted as valid. Because the path was treated as known, the device would show or sign with it without warning, even when the path belonged to one cryptocurrency (e.g., Bitcoin) but was used on another (e.g., Litecoin or Testnet). The fix makes the firmware reject this leftover pattern as an unknown path, matching the behavior of newer Trezor Core firmware.

Security candidaterefactor(core/caesar): rm unused ButtonPage buildersby obrusvit · f5ec3bba · Oct 22, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · obrusvit

refactor(core/caesar): rm unused ButtonPage builders

- `with_back_btn` and `with_next_btn` have no callers since the new
menu navigation, the up and down arrows are used directly.

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

This is a routine code cleanup. The developer removed two unused configuration options (back button and next button) from a screen-page component in the Trezor firmware's user interface. The buttons are now created directly where needed, with the same up-arrow and down-arrow icons as before. There is no functional change and no security relevance.

Security candidatefix(core/fido2): unlock before handling `_CBOR_RESET`by Roman Zeyde · c6e5deaa · Oct 22, 2026 · 1 fileMessage 89 · StrongLow 42Details
Commit message · Roman Zeyde

fix(core/fido2): unlock before handling `_CBOR_RESET`

Otherwise, the storage is locked - credentials cannot be deleted.

[no changelog]

89/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode
Why it was queued
credential or privilege stateauthentication path
AI analysis · Low 42/100

This commit fixes a bug in the Trezor device's FIDO2 (WebAuthn/passwordless login) feature. Before the fix, if a user tried to perform a factory reset of FIDO2 credentials while the device storage was locked (for example, after auto-lock or reboot), the reset could not actually delete the stored credentials because the code skipped the unlock step. The fix ensures the device prompts for the PIN to unlock storage before processing the reset, so credentials can be properly wiped.

Security candidatefix(core/secmon): block smcalls invoked from unprivileged modeby cepetr · 6f1ab9a0 · Oct 22, 2026 · 1 fileMessage 62 · AdequateHigh 76Details
Commit message · cepetr

fix(core/secmon): block smcalls invoked from unprivileged mode

[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
credential or privilege state
AI analysis · High 76/100

This commit fixes a security hole in the Trezor hardware wallet's secure monitor (secmom). The secure monitor is a trusted piece of firmware that handles sensitive 'smcall' requests. Previously, these calls could be made from unprivileged (less trusted) code. The patch now blocks smcalls from unprivileged mode and triggers a fatal error or reboot if such a call is attempted. This prevents untrusted code from tricking the secure monitor into performing privileged operations.

Security candidatefeat(core/delizia): allow external menu with holdby Jakub Janků · 24ec8d8e · Oct 22, 2026 · 4 filesMessage 80 · StrongInformational 16Details
Commit message · Jakub Janků

feat(core/delizia): allow external menu with hold

Allow an external menu together with hold in Delizia `confirm_action`.
Without any text to show, display only the hold prompt, with `verb` as
its footer.

[no changelog]

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

This commit changes how a confirmation screen behaves on the Trezor Safe 5 (Delizia) when there is no text to display and the user must hold a button to confirm. It allows an external menu to appear alongside the hold-to-confirm prompt, and uses a custom label (verb) as the on-screen footer. The change is a UI feature, not a fix for a known exploit, and the commit message does not claim any security relevance.

Security candidatefeat(core): add danger style to confirm_actionby Jakub Janků · edf88e68 · Oct 22, 2026 · 16 filesMessage 80 · StrongInformational 15Details
Commit message · Jakub Janků

feat(core): add danger style to confirm_action

Turn `hold_danger` into a general `danger` style. Besides the hold
button, it marks the title on Delizia and Eckhart, and the confirm
button on Bolt and Eckhart. This also restyles the wipe device and
experimental features confirmations.

[no changelog]

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

This commit is a user-interface styling change. It renames a parameter from 'hold_danger' to 'danger' and applies a warning/danger visual style (red/orange colors, warning icons) to screens that already required the user to hold a button to confirm risky actions like wiping the device or enabling experimental features. There is no change to security logic, cryptography, or how confirmations are enforced.

Security candidatefeat(solana): allow skipping the reviewby Jakub Janků · 0b837f51 · Oct 22, 2026 · 12 filesMessage 80 · StrongLow 41Details
Commit message · Jakub Janků

feat(solana): allow skipping the review

A lengthy review may run into timeouts on the host. On Delizia and
Eckhart, the blind signing warning offers skipping the review in its
menu. A skipped review ends on a blind signing screen, from whose menu
the user can still return to the details.

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 boundarycryptography-sensitive pathsigning or wallet path
AI analysis · Low 41/100

This commit adds a new user-interface option for Solana transactions on newer Trezor models (Delizia and Eckhart). When a transaction contains unknown instructions and must be 'blind signed,' the device now offers a menu item that lets the user skip reviewing the lengthy details and go straight to signing. The change is presented as a usability fix to avoid host-side timeouts during long reviews, not as a security fix. Older layouts (Bolt, Caesar) keep the previous behavior and do not offer the skip.

Security candidatechore(core): adapt to mldsa-native v2.0.0by M1nd3r · ba5e0a5d · Oct 21, 2026 · 6 filesMessage 95 · StrongInformational 16Details
Commit message · M1nd3r

chore(core): adapt to mldsa-native v2.0.0

- Removed `siglen` from signing/verification.
- Signature size is now checked in prodtest before signature verification.
- Added `src/polyvec_lazy.c` to be compiled.
- Renamed `MLD_CONFIG_API_PARAMETER_SET` to `MLD_CONFIG_PARAMETER_SET`.

[no changelog]

95/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validationcryptography-sensitive pathboot or update path
AI analysis · Informational 16/100

This is a routine maintenance update that adapts Trezor's firmware code to version 2.0.0 of an external cryptographic library called mldsa-native. It mainly renames configuration constants, removes an unnecessary signature-length parameter from function calls, and adds a signature-size check in the production-test verification path. There is no direct evidence in the commit that this fixes an active security vulnerability.

Security candidaterefactor(core/bootloader): commit the firmware version separately from checking it [no changelog]by tychovrahe · 81fe6aec · Oct 21, 2026 · 3 filesMessage 95 · StrongModerate 63Details
Commit message · tychovrahe

refactor(core/bootloader): commit the firmware version separately from checking it [no changelog]

fw_check() committed the header's monotonic version to the rollback
counter as a side effect, before it verified the image contents. Every
status query that called it wrote to the device: GetFeatures over the
wire, and now the debug link too, which is serviced during an upload
when the image in flash is half-written.

fw_check() is read-only now and reports version_trusted and monotonic
in its result; the boot path commits them through fw_commit_min_version()
right after the check, under the same condition and at the same point
as before. The pre-jump re-verification keeps its own commit. The update
flow never committed, so after an install the version is committed by
the reboot that follows, as it always was when the host sent no
GetFeatures in between.

Co-Authored-By: Claude Fable 5.1 <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 trustdefensive validationboot or update path
AI analysis · Moderate 63/100

This bootloader change fixes a side effect where simply asking the device for its status could permanently change a security counter on the device. Before, a routine called fw_check() both inspected the firmware and updated the rollback counter. Now the inspection is read-only, and the actual update is done only at deliberate points such as booting. This prevents a half-written firmware update or a status query from locking the device to a version before the firmware is fully verified and installed.

Security candidatefeat(core): start apps via coreapp_app_entry()by Lukas Bielesch · 37d70ad8 · Oct 21, 2026 · 8 filesMessage 57 · ThinLow 27Details
Commit message · Lukas Bielesch

feat(core): start apps via coreapp_app_entry()

[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 · Low 27/100

This commit changes how apps are launched on Trezor hardware wallets. Instead of jumping directly into an app's main function, the firmware now first runs a small Core-provided entry point that sets up the app's memory allocator and then calls the app's main function. This is a structural improvement that lets Core control more of the app's startup environment, but the commit itself does not fix a known bug or vulnerability.

Security candidatetest(core): test chacha20poly1305 state machineby Andrew Kozlik · 40e4bdb3 · Oct 21, 2026 · 1 fileMessage 82 · StrongInformational 12Details
Commit message · Andrew Kozlik

test(core): test chacha20poly1305 state machine

[no changelog]

Co-Authored-By: Claude Opus 5.5 <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 path
AI analysis · Informational 12/100

This commit only adds new automated tests for the ChaCha20-Poly1305 encryption helper in Trezor's firmware. It checks that the code correctly rejects wrong key lengths, wrong nonce lengths, and invalid calling sequences (for example, calling auth twice or feeding data after the stream has finished). There are no changes to the actual encryption implementation, so this commit does not introduce or fix a security vulnerability by itself.