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.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
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.
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…
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…
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…
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)
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…
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
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
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…
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.
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
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…
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…
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
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 …
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…
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
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
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 …
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
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedchore(ethereum): move lookup_address logic to helperby PrisionMike · 55e6d13c · Oct 24, 2026 · 4 filesMessage 62 · AdequateInformational 15Details
Commit message · PrisionMike
chore(ethereum): move lookup_address logic to helper
[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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a simple internal code cleanup: it moves a helper function that looks up well-known Ethereum smart contract names from one file to another and renames a private generator function to be public. There is no change to user-facing behavior, no bug fix, and no security improvement or regression.
AI review queuedchore(translations): sync Crowdin translationsby Thalarion · 30f0d820 · Oct 23, 2026 · 7 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion
chore(translations): sync Crowdin translations
[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 or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine synchronization of translated user-interface text strings from the Crowdin translation platform into the Trezor firmware. It only changes wording, grammar, and layout of on-screen messages in multiple language files. There is no code logic change, no security fix, and no functional behavior change.
Lower-priorityfeat(core/delizia): static header iconby Jakub Janků · 40722b4f · Oct 23, 2026 · 1 fileMessage 92 · StrongTriage 0Details
Commit message · Jakub Janků
feat(core/delizia): static header icon
Add `Header::with_icon`, an icon left of the title that, unlike the animated result icon, takes space from the title so that it wraps next to the icon.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
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.
- 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.
Lower-priorityci: build firmware on every push to mainby tychovrahe · 6f320a46 · Oct 23, 2026 · 1 fileMessage 92 · StrongTriage 0Details
Commit message · tychovrahe
ci: build firmware on every push to main
- reference builds so that a PR's binary sizes can be compared against the exact main commit it was merged with - upload the linker map files next to the binaries and ELFs - every job other than the firmware build is skipped for pushes to main; the unsigned firmware archive stays limited to release branches - T2B1 is built only on release pushes so that main builds produce the same artifact set as PR builds
[no changelog]
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
documentation-only discount
Lower-priorityfix(core): reject an out-of-range refresh index in Display.record_start [no changelog]by tychovrahe · 9c4a9d43 · Oct 23, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · tychovrahe
fix(core): reject an out-of-range refresh index in Display.record_start [no changelog]
The recording API takes a uint32_t; a negative or oversized Python value would have wrapped. Raise ValueError instead.
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
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(core): fix deadlock on fault with bad task SPby cepetr · 39ee91e8 · Oct 22, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · cepetr
fix(core): fix deadlock on fault with bad task SP
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci(core): increase upgrade test timeout a bitby Roman Zeyde · 2c9babe7 · Oct 22, 2026 · 1 fileMessage 94 · StrongTriage 0Details
Commit message · Roman Zeyde
ci(core): increase upgrade test timeout a bit
Also, use lower pytest timeout, to avoid CI job cancellation
[no changelog]
94/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode✓ Mentions testing or verification
(cherry picked from commit 23578abef19de557c60423755a9903ec79624c74)
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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 39/100
This commit fixes how Trezor hardware wallets estimate Solana transaction priority fees when the user does not set an explicit compute-unit limit. Previously the code always assumed a flat 200,000 compute units, which could make the displayed fee much lower or much higher than what the Solana network would actually charge. The patch now follows Solana's real rules: built-in programs cost 3,000 units each, unknown programs cost 200,000 units each, and the total is capped at 1.4 million units. It also rejects duplicate compute-budget instructions, matching what the Solana runtime does. The main risk is that a user might approve a transaction based on an incorrect fee estimate, but the actual funds moved still depend on the transaction's instructions, not the estimate.
- `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.
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.
Lower-prioritychore(core): check the style of the core scriptsby Ondřej Vejpustek · d826506f · Oct 22, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Ondřej Vejpustek
chore(core): check the style of the core scripts
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritystyle(core): drop the formatting exemption in `emu.py`by Ondřej Vejpustek · 630c163c · Oct 22, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Ondřej Vejpustek
style(core): drop the formatting exemption in `emu.py`
The file is not formatted automatically.
[no changelog]
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-prioritystyle(core): make `emu.py` pass the style checksby Ondřej Vejpustek · e2326e5a · Oct 22, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Ondřej Vejpustek
style(core): make `emu.py` pass the style checks
[no changelog]
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
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.
AI review queuedchore(env): add `zlib` to `LD_LIBRARY_PATH`by M1nd3r · d23a6709 · Oct 22, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · M1nd3r
chore(env): add `zlib` to `LD_LIBRARY_PATH`
- Needed by the pillow dependency.
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
second-pass: broader security terminology
AI analysis · Informational 15/100
This is a routine build-environment change that adds the zlib compression library to a runtime library search path so the Python Pillow imaging library can find it. There is no indication of a security vulnerability, fix, or behavior change in the firmware itself.
Lower-prioritychore(deps): update certifi, pillow, and virtualenvby M1nd3r · bbedc9cd · Oct 22, 2026 · 2 filesMessage 98 · StrongTriage 0Details
Commit message · M1nd3r
chore(deps): update certifi, pillow, and virtualenv
✓ 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✓ Names security-relevant behavior explicitly
Why it was queued
automated dependency-update discount
Lower-priorityfix(core/embed): harden `printf` to avoid ASAN failuresby Roman Zeyde · 45a6c861 · Oct 22, 2026 · 1 fileMessage 100 · StrongTriage 8Details
Commit message · Roman Zeyde
fix(core/embed): harden `printf` to avoid ASAN failures
[no changelog]
(cherry picked from upstream fix commit https://github.com/eyalroz/printf/commit/a4434bcd35caedf3354eb12e943255331f8c53fa)
100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
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.