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
✓ 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 routine cleanup: it removes the 'ª' (feminine ordinal indicator) character from font files and a code generator list because it is no longer used in the Portuguese-Brazil translation. There is no security relevance.
Security candidatechore(translations): removed unused ES glyphby Michal Kazda · 8d2264c8 · Aug 26, 2026 · 24 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda
chore(translations): removed unused ES glyph [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 removes the unused Spanish masculine ordinal indicator glyph (º) from font files and a code generator list. It is a routine cleanup with no security relevance.
This commit is a routine cleanup of unused French font data. It removes the degree symbol (°) glyph and its spacing rules from 23 font files because that character is no longer needed for French translations. There is no code change, no security fix, and no user-facing behavior change beyond slightly smaller font files.
Security candidatefeat: Introduce dynamic parameter handling for device menu layouts and longer lifetimeby Vojtěch Nevřela · 8d01a0b1 · Aug 26, 2026 · 15 filesMessage 85 · StrongInformational 19Details
Commit message · Vojtěch Nevřela
feat: Introduce dynamic parameter handling for device menu layouts and longer lifetime
- Added `ParamsObj` struct to encapsulate fresh construction parameters for layouts. - Implemented `request_params` method in `EventCtx` to signal the need for updated parameters. - Updated `DeviceMenuScreen` to handle parameter updates without restarting the layout. - Refactored `show_device_menu` method signatures across multiple firmware implementations to accept a single `DeviceMenuParams` struct. - Enhanced the `DeviceMenuParams` struct to facilitate easier parameter management and parsing from MicroPython dictionaries. - Removed obsolete `RefreshMenu` message from `DeviceMenuMsg` and related handling. - Updated Python interface to support new parameter handling in device menu interactions.
[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
signing boundarycryptography-sensitive pathboot or update path
AI analysis · Informational 19/100
This commit is a user-interface refactor for the Trezor hardware wallet's device menu. It changes how the menu receives updated information (like Bluetooth connection status) so the menu can refresh itself without closing and reopening. There is no direct evidence in the commit that this fixes a security vulnerability; it appears to be a code-quality and user-experience improvement.
✓ 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 routine cleanup that removes duplicate or unnecessary function and variable declarations across many source files. It does not change how the device behaves, process secrets, or handle user data. There is no indication this is a security fix.
fix(core): reorder linker script sections for stm32f4 firmware
[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 · Low 43/100
This commit moves a special memory section named '.bootloader' from one flash memory region to another in the firmware's build instructions (the linker script). The bootloader section likely contains data used to verify or locate the device's bootloader. Reordering linker sections can affect how the firmware is laid out in memory, which in rare cases can have security implications (for example, if it changes what code runs first, where secrets live, or how integrity checks are computed). However, the commit message gives no explanation of why the change was needed or whether it fixes a security problem, and the diff alone does not show a clear vulnerability.
chore(clear_signing): delete inbuilt 1inch and uniswap definitions.
Needs full regression testing with Suite 1inch swaps.
[no changelog]
87/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
Why it was queued
signing boundaryfuzzing or regression evidencesigning or wallet path
AI analysis · Low 34/100
This commit removes built-in human-readable display definitions for 1inch and Uniswap swap transactions from Trezor's Ethereum clear-signing feature. Without these definitions, Trezor devices will likely fall back to showing raw contract call data for those transactions, making it harder for users to verify what they are signing. It is a feature-removal change, not a direct code vulnerability, but it weakens a security-relevant usability safeguard.
Security candidaterefactor(core/ui): build bootloader screens without duplicating the partsby tychovrahe · 1e57cc9d · Aug 25, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · tychovrahe
refactor(core/ui): build bootloader screens without duplicating the parts
Two size-driven cleanups in the delizia bootloader screens, both behaviour-identical.
screen_install_confirm built TWO complete button pairs -- one with text, one with icons -- and picked between them. Both branches used the same styles and the same alignment, so `Button::with_text`/`with_icon` plus their whole styling chain were instantiated twice. Select the ButtonContent first, then build each button once.
screen_intro and screen_install_confirm assembled their strings with one `unwrap!` per `push_str` -- ten panic sites between them, each carrying its own location string, for strings that are either built whole or not at all. A `bld_string` helper gives one shared site and reads better than the chain it replaces.
160 B on T3T1
[no changelog]
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 15/100
This is a code cleanup that makes two bootloader screens slightly smaller and easier to read. It does not change what the device does or how it behaves, and it does not fix any security bug.
✓ 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 fixes a build failure that occurred when compiling Trezor firmware with the --debug option. It adds explicit references to the 'sys' Rust module so the linker includes necessary symbols such as the panic handler. There is no indication this change addresses a security vulnerability or runtime behavior in release builds.
Security candidatefeat(common,core,python): support Stellar delegated authentication.by Jun Luo · e17e1141 · Aug 24, 2026 · 14 filesMessage 67 · AdequateLow 30Details
Commit message · Jun Luo
feat(common,core,python): support Stellar delegated authentication.
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 controlsigning or wallet path
AI analysis · Low 30/100
This commit adds support for a new Stellar blockchain feature called delegated authentication (CAP-71-01 / Protocol 27). It lets an account authorize a transaction through a chain of delegated signers. The device now recognizes and serializes these delegate chains, but when showing the transaction to the user it only displays the top-level authorizing address, not the individual delegates. This is a normal feature addition; there is no direct evidence in the commit of a security vulnerability, though any new signing path deserves careful review.
fix(core): centralize rust panic handler in sys crate
[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 12/100
This commit is a code cleanup: it moves the Rust panic handler from several individual firmware components into a single shared system crate. A panic handler is the code that runs when something goes seriously wrong inside the device software. The change does not add new functionality or fix a security bug; it just makes the panic handling code live in one place instead of many. The release builds of Trezor firmware do not even use this handler because they are configured to abort immediately on panic.
Security candidatefeat(core): enable menu to return arbitrary valuesby Vojtěch Nevřela · e9869dbf · Aug 24, 2026 · 15 filesMessage 85 · StrongInformational 19Details
Commit message · Vojtěch Nevřela
feat(core): enable menu to return arbitrary values
[no changelog]
Enables the Menu to return arbitrary values in preparation for UI cleanup and modularisation.
This commit is only internal refactor, should have no functional effect.
[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 pathboot or update path
AI analysis · Informational 19/100
This commit is an internal user-interface refactor for Trezor firmware. It changes how on-screen menus are built so that each menu entry can carry an 'intent' (standard or danger) and can return arbitrary values, instead of only supporting a fixed cancel button. The commit message and diff show no new user-facing behavior; existing cancel buttons are converted into a new 'cancel leaf' abstraction. There is no direct evidence this introduces a security vulnerability, but any refactor that touches workflow cancellation paths deserves a careful look to ensure users can still abort dangerous actions.
Security candidatefix(solana): don't present trailing accounts as multisig signersby Jakub Janků · a59ace76 · Aug 23, 2026 · 18 filesMessage 98 · StrongHigh 76Details
Commit message · Jakub Janků
fix(solana): don't present trailing accounts as multisig signers
Token program instructions accept trailing account references beyond their declared account list. The device labeled every such account "Signer N" and warned that "the following instruction is a multisig instruction". Neither claim can be verified on-device:
- Whether an account must co-sign is a message-level fact (its signer flag), which was never checked. A host could append arbitrary read-only accounts (silently ignored by the Token program unless they match a multisig member) or ALT-referenced accounts (which can never sign) and the device would present them as required co-signers. E.g. for a 1-of-N multisig, a transfer could be made to appear to require another party's approval while it actually executes on the user's signature alone. - Whether the operation is a multisig operation at all depends on on-chain state (the owner account's program-owner and data length): trailing signers attached to a plain single-sig owner are ignored entirely, yet the multisig warning was still shown.
See validate_owner in the Token-2022 processor for both behaviors: https://github.com/solana-program/token-2022/blob/426400f29d5f1e299be8b353fdf13f22358fbd68/program/src/processor.rs#L2264-L2293
Instead of interpreting the trailing accounts, display only what the message provably says:
- List every trailing account with its actual (Writable/Signer) flags, in the same format the unknown-instruction view already uses. The signer flag is enforced by the runtime (the transaction is rejected without that account's signature), so this display cannot be spoofed by the host. - Drop the per-instruction multisig warning. It asserted an unverifiable interpretation, and the transaction-level "requires N signers" warning already fires in every case where multiple signatures are in fact required. - InitializeMultisig: fold the "signer_accounts" reference into the trailing list. The trailing accounts of this instruction are the future multisig members (read-only, no signatures required at creation), and the first member was previously labeled differently ("Signers") from the rest ("Signer 1", "Signer 2", ...). The at-least-one-member requirement is no longer enforced on-device; a violating transaction fails on-chain. https://docs.rs/spl-token-2022-interface/3.1.1/spl_token_2022_interface/instruction/enum.TokenInstruction.html#variant.InitializeMultisig - Rename is_multisig -> trailing_references (programs.json) and multisig_signers -> trailing_accounts, since the mechanism is "instruction may carry extra account references", not anything multisig-specific (System Program Transfer uses it too).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> (cherry picked from commit 94af18581f3c5a3825bd366c0fdaccdc29e91d11)
98/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✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validationsigning or wallet path
AI analysis · High 76/100
This update fixes a Trezor Solana display bug that could mislead users into believing a transaction needed extra approvals when it did not. The device previously labeled any extra account attached to certain Solana instructions as a required 'Signer' and warned that the instruction was a multisig instruction, even when those accounts were not signers, not multisig members, or did not exist on-chain. The fix now shows each extra account with its real on-message flags (Writable/Signer), and removes the unverifiable per-instruction multisig warning. This prevents a malicious or buggy host app from making a single-signature transfer look like a multi-signature transfer.
Security candidatechore(core): export `USE_NFC` from `trezor.utils`by Roman Zeyde · 5d4fe90a · Aug 23, 2026 · 9 filesMessage 72 · AdequateInformational 15Details
Commit message · Roman Zeyde
chore(core): export `USE_NFC` from `trezor.utils`
Also, don't return NFC capability (until the driver is stable).
[no changelog]
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100
This is a routine feature-flag plumbing change for an upcoming NFC hardware feature. It exposes a new USE_NFC constant in Python code and disables advertising NFC capability to host software until the NFC driver is considered stable. There is no security bug or vulnerability in the diff.
Security candidatefeat(core/stellar): show trusted SEP-41 token contracts as token operations.by Jakub Janků · 177f3fe2 · Aug 23, 2026 · 6 filesMessage 100 · StrongLow 30Details
Commit message · Jakub Janků
feat(core/stellar): show trusted SEP-41 token contracts as token operations.
The token UI was reachable only for a Stellar Asset Contract, whose asset the host can point out and the device can verify by re-deriving the contract address. A token that is only a SEP-41 contract cannot be identified that way, so its transfers showed up as an opaque contract call.
Add a hardcoded, network-bound list of vetted contracts, starting with SolvBTC and xSolvBTC. Symbol and precision are what the contracts report, but both are upgradeable, so this is a trust decision rather than a proof. A Stellar Asset Contract still takes precedence, since its hint proves the contract's identity.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
100/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✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 30/100
This commit improves how the Trezor hardware wallet displays certain Stellar token transactions on its screen. Previously, some token transfers looked like confusing generic contract calls. Now, for two specific vetted tokens (SolvBTC and xSolvBTC), the device will show a friendly token transfer screen. This is a user-interface improvement based on a hardcoded trust list, not a fix for a code execution or theft vulnerability. The change does not alter what transactions the device will or won't sign.
Security candidaterefactor(core/stellar): describe amounts with StellarToken instead of StellarAsset.by Jakub Janků · 588f6f32 · Aug 23, 2026 · 9 filesMessage 85 · StrongInformational 12Details
Commit message · Jakub Janků
refactor(core/stellar): describe amounts with StellarToken instead of StellarAsset.
A SEP-41 token need not be backed by a classic asset, so StellarAsset cannot describe one: it carries no precision, and a token that is not a Stellar Asset Contract has no issuer. StellarToken holds just what the screens need -- symbol, precision, optional issuer -- and formats amounts with its own precision, replacing format_asset and the 7-decimal assumption in format_amount.
No behavior change: every token still resolves to seven decimals.
[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
cryptography-sensitive path
AI analysis · Informational 12/100
This is a code cleanup (refactor) in the Stellar cryptocurrency support. It replaces an older way of describing tokens on screen with a new internal data structure, but explicitly keeps the same user-visible behavior: every token is still shown with seven decimal places. The change also adds a test confirming that for the native Stellar asset (XLM), any code or issuer supplied by a host computer is ignored, preventing a host from mislabeling XLM as another asset. There is no indication this fixes an active security bug; it is preparation for future SEP-41 token support.
Security candidatefeat(core/prodtest): Update to new noise lib version + add card certificitate authenticity check.by kopecdav · 0d424c69 · Aug 22, 2026 · 2 filesMessage 62 · AdequateInformational 22Details
Commit message · kopecdav
feat(core/prodtest): Update to new noise lib version + add card certificitate authenticity check.
[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 path
AI analysis · Informational 22/100
This commit updates a factory-testing tool (prodtest) used with Trezor hardware wallets. It swaps a randomly generated test key for a fixed, hard-coded test keypair and adds a check that the public key reported by an NFC backup card matches the public key in the card's certificate. The change is in a production-test utility, not normal user firmware, and the hard-coded key appears to be a test fixture rather than a live secret. The added certificate check is a security-hardening step, but the commit is partial: it references a new noise_xxpsk3.c source file and a new library API without showing the implementation.
Security candidatefeat(core/ethereum): support EIP-7702 delegation for `Simple7702Account`by Roman Zeyde · 255787a9 · Aug 22, 2026 · 5 filesMessage 100 · StrongInformational 20Details
Commit message · Roman Zeyde
feat(core/ethereum): support EIP-7702 delegation for `Simple7702Account`
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathauthentication path
AI analysis · Informational 20/100
This commit adds support for recognizing one more Ethereum smart-contract account type (Simple7702Account) when signing EIP-7702 delegation authorizations on Trezor hardware wallets. It is a small feature addition that updates a known-address lookup table and adds matching test vectors. There is no indication it fixes a security bug or introduces a vulnerability.
Security candidaterefactor(core/ui): require the amount and the asset in confirm_stellar_output.by Jakub Janků · a8648775 · Aug 21, 2026 · 4 filesMessage 85 · StrongLow 27Details
Commit message · Jakub Janků
refactor(core/ui): require the amount and the asset in confirm_stellar_output.
Both have been optional since the function was introduced, but no caller ever omitted them, and the guard would have silently shown a recipient with no amount.
[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
cryptography-sensitive path
AI analysis · Low 27/100
This change tightens a Stellar cryptocurrency confirmation screen so the amount and asset can no longer be left blank. Previously, the code allowed them to be optional and would silently skip showing the amount if either was missing, which could let a user approve a payment without seeing how much was being sent. The commit makes both values mandatory and always displays them. It is described as a defensive refactor, not a fix for an active bug or reported vulnerability.
to reliably locate built artifacts, without relying on $OUT_DIR/../../.. (which is not guaranteed stable across cargo versions) (neither is the current method but at least now we have a central place to fix further breakage)
70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · Informational 15/100
This is a build-system maintenance change. It replaces hard-coded guesses about where Cargo places compiled files with a single helper function that walks the directory tree more reliably. There is no user-facing feature change and no security fix or vulnerability.
Security candidatechore: rename `N4W1` to `N1W1`by Roman Zeyde · 33b92f48 · Aug 20, 2026 · 51 filesMessage 80 · StrongInformational 15Details
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update path
AI analysis · Informational 15/100
This commit is a simple bulk rename of an internal feature code name from 'N4W1' to 'N1W1' across the Trezor firmware codebase, build system, tests, and client libraries. It changes only identifiers, comments, strings, and generated protocol-buffer files. There is no functional change and no security relevance.
✓ 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 · Low 46/100
This commit adds a new security gate inside the Trezor firmware's core operating system. Before this change, any installed mini-program ('applet') could call any internal system function ('syscall'). Now, by default, applets can only call a small, approved list of syscalls, unless they are explicitly granted a new 'unlimited_syscalls' privilege. The built-in 'coreapp' applet is granted this privilege, so it behaves as before. The change is a hardening measure that reduces the damage a compromised or malicious applet could do.
✓ 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 · Low 46/100
This commit adds a new security permission called framebuffer_access that controls whether a small helper app (applet) running on the Trezor can read from or write to the device's screen memory. Previously, applets could access the framebuffer based only on memory location checks. Now they must also be explicitly granted the framebuffer_access privilege. The change is a hardening/feature addition, not a fix for an active exploit, and it removes an older privilege called assets_area_access that was apparently unused or being replaced.
Security candidaterefactor(core/rust): fix Layout::return_value() after Error is no longer Cloneby matejcik · e6e9ec08 · Aug 20, 2026 · 5 filesMessage 62 · AdequateLow 26Details
Commit message · matejcik
refactor(core/rust): fix Layout::return_value() after Error is no longer Clone
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 · Low 26/100
This commit is a small internal code cleanup in the Trezor firmware's Rust UI layer. It changes how a layout object hands back its result to caller code: instead of returning a copy of the result, it now 'takes' the result away so the same value cannot be retrieved twice. The change was needed because the error type no longer supports being copied (Clone). There is no direct evidence in the commit that this fixes an exploitable security bug; it appears to be a refactoring to keep the code compiling and to make the API behavior clearer (subsequent calls return None).
Security candidatefeat(rust/micropython): more ergonomic tuplesby matejcik · 89e4ee10 · Aug 20, 2026 · 11 filesMessage 57 · ThinInformational 15Details
Commit message · matejcik
feat(rust/micropython): more ergonomic tuples
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 routine internal code cleanup in the Trezor firmware's Rust/MicroPython bridge. It introduces a dedicated tuple helper module so developers can write tuple conversions more naturally, and removes an older, less ergonomic helper. There is no indication it fixes a security bug or changes security-relevant behavior.