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.
Security candidatefix(legacy): align coinjoin behavior with coreby Andrew Kozlik · e1463ec0 · Aug 11, 2026 · 5 filesMessage 85 · StrongLow 35Details
Commit message · Andrew Kozlik
fix(legacy): align coinjoin behavior with core
An authorization granted by DoPreauthorized was consumed by whatever message arrived next, and the same applied to a path unlocked by UnlockPath. Core allows a coinjoin preauthorization to be used only by SignTx and GetOwnershipProof, and an unlocked path only by GetAddress, GetPublicKey and SignTx. Apply the same allowlists by dropping the authorization before dispatching a message it does not apply to, which reproduces core's behavior of aborting the workflow and reprocessing the message as a new one.
This is defense in depth rather than a fix for a reachable issue. The authorization is stored per session, so whoever can use it is the host that ran AuthorizeCoinJoin, which already holds the SLIP-25 xpub from a confirmed UnlockPath. Without the allowlist a coinjoin authorization additionally let GetAddress and GetOwnershipId reach the SLIP-25 external chain without the coinjoin account access confirmation. The xpub was never exposed, as GetPublicKey checks unlock_path directly.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
access controlboot or update pathauthentication path
AI analysis · Low 35/100
This commit tightens access controls in the older Trezor firmware (legacy) for a privacy feature called CoinJoin. Previously, after a host app was pre-authorized, any next message could consume that authorization. Now only specific message types (SignTx and GetOwnershipProof for preauthorization; GetAddress, GetPublicKey, and SignTx for an unlocked path) can use it. The vendor describes this as defense in depth, not a fix for a directly reachable attack, because the host that could trigger it already has related access. Still, without the change, a preauthorization could let GetAddress or GetOwnershipId touch the CoinJoin account without showing the user the usual confirmation screen.
AI review queuedfix(core): nostr string serializationby Martin Milata · 1239c9e1 · Aug 11, 2026 · 3 filesMessage 57 · ThinModerate 60Details
Commit message · Martin Milata
fix(core): nostr string serialization
[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 pathsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
This commit fixes a bug in how the Trezor hardware wallet builds Nostr event signatures. Previously, special characters in the event content and tags (like quotes, backslashes, tabs, and newlines) were not properly escaped when creating the JSON string that gets signed. This could cause the device to compute a signature that does not match what standard Nostr software expects, or in some cases could allow a malicious app to craft content that changes the meaning of what the user approved on screen versus what is actually signed. The fix adds proper JSON string escaping for both the main content and tag strings.
Security candidatefix(legacy): abort on coinjoin coin-name mismatchby Andrew Kozlik · afc6ebe3 · Aug 11, 2026 · 3 filesMessage 80 · StrongLow 34Details
Commit message · Andrew Kozlik
fix(legacy): abort on coinjoin coin-name mismatch
Enforces a check aligning the behavior with core. The missing check did not yield anything an attacker couldn't get from a legitimate coinjoin round on the authorized coin. The inputs signed are always from the authorized SLIP-25 account regardless of what coin_name claims.
Co-Authored-By: Claude Opus 4.8 <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
explicit security languagesigning or wallet pathboot or update pathauthentication path
AI analysis · Low 34/100
This commit fixes a bug in the older Trezor firmware (legacy) where a CoinJoin signing session would not be properly aborted if the requested coin name did not match the one in the prior authorization. Before the fix, the device sent an error message but continued processing, which could allow a malicious or mismatched transaction to proceed. The fix adds an explicit abort and return so the signing stops immediately, matching the behavior of newer Trezor firmware (core). The commit message downplays the practical risk, noting an attacker could not gain more than from a legitimate CoinJoin on the authorized coin.
Security candidatechore(core/ethereum): drop `EthereumSignAuth7702` and its handlerby Roman Zeyde · bd6186c4 · Aug 11, 2026 · 17 filesMessage 77 · AdequateInformational 15Details
Commit message · Roman Zeyde
chore(core/ethereum): drop `EthereumSignAuth7702` and its handler
It will be integrated into `EthereumSignTxEIP1559`.
[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 or wallet pathauthentication path
AI analysis · Informational 15/100
This commit removes an Ethereum feature called EthereumSignAuth7702 from the Trezor firmware and related software. It deletes the message types, the signing handler, the command-line tool, and the tests. The commit message says this feature will later be merged into EthereumSignTxEIP1559. There is no security fix here—this is a routine cleanup/refactoring change.
✓ 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
defensive validationcryptography-sensitive path
AI analysis · Moderate 59/100
This commit adds validation checks to Trezor's cryptocurrency wallet code to make sure private and public keys are mathematically valid before they are used. Previously, some code paths accepted invalid keys (such as a private key of zero, a private key equal to or larger than the curve order, or a public key that is not actually a point on the elliptic curve). Using invalid keys could in theory lead to incorrect cryptographic operations or weaken security. The change also fixes a missing check for unknown curve names during deserialization, which could have caused the code to read from a null pointer.
AI review queuedfix(solana): fall back to generic UI for more ALT referencesby Jakub Janků · cd6e7596 · Aug 11, 2026 · 4 filesMessage 93 · StrongModerate 61Details
Commit message · Jakub Janků
fix(solana): fall back to generic UI for more ALT references
transfer_token_instruction.token_mint and transfer_token_instruction.owner can be Address Lookup Table (ALT) references. Previously, the predefined token transfer flow would misleadingly display just the ALT address. The user thus couldn't distinguish an actual address from an ALT reference. Now, the handler falls back to the generic ALT-aware confirmation UI.
537b34f847f8e3f97e4444be9f8f50706ac34075 added a check for transfer_token_instruction.destination_account, but omitted the token_mint and owner fields which can be ALT references as well.
(cherry picked from commit b992a24a93d77066b3ac2fec1dae7129d09427d1)
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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 61/100
This update fixes a display bug in Trezor's Solana token-transfer confirmation screen. When a token transfer uses Solana Address Lookup Tables (ALTs) to refer to the token mint or the owner account, the device previously showed the lookup-table address as if it were the real account address. That could trick a user into approving a transfer they did not fully understand. The fix makes these cases fall back to a more cautious, generic confirmation screen that clearly marks ALT references.
Security candidatetest(core/ethereum): adjust EIP-7702 test vectorsby Roman Zeyde · d5dea04b · Aug 11, 2026 · 3 filesMessage 90 · StrongInformational 15Details
Commit message · Roman Zeyde
test(core/ethereum): adjust EIP-7702 test vectors
- rename `nonce` to `tuple_nonce` since it's not the same as the tx nonce - set `to_address` to `m/44'/60'/0'/0/0`-derived address - test non-empty calldata, empty destination and payment request - update `chain_id` 0 error message - add mainnet test vectors
[no changelog]
90/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
Why it was queued
fuzzing or regression evidencesigning or wallet pathauthentication path
AI analysis · Informational 15/100
This commit only updates test data files for Ethereum EIP-7702 (account abstraction) signing. It renames a test field, adds more test cases, updates expected error messages, and adds mainnet transaction test vectors. There are no changes to the actual firmware or production code, so it does not introduce or fix a security vulnerability in the shipped product.
AI review queuedfix(solana): fall back to generic UI if stake lockup setby Jakub Janků · 5a530509 · Aug 11, 2026 · 2 filesMessage 93 · StrongModerate 60Details
Commit message · Jakub Janků
fix(solana): fall back to generic UI if stake lockup set
Prior to this change, the predefined staking flow allowed lockup.custodian = _SYSTEM_PROGRAM_ID, lockup.epoch > 0, and lockup.unix_timestamp > 0. However, these values were not displayed to the user. This could lead to the user loosing access to their funds if the time values were set to distant future.
The change should not modify the behavior when working with Suite since it generates init instructions with lockup.epoch=0 and lockup.unix_timestamp=0:
(cherry picked from commit 5a12ad231741e0406f9d7f7a0b2e15a7237f0bbd)
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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
This update fixes a security gap in Trezor's handling of Solana staking. Previously, if someone set up a stake account with a future unlock date (a 'lockup') using values that Trezor's normal flow didn't expect, the device would silently approve the transaction without showing those lockup details on screen. That could trap a user's funds until a far-future date. The fix makes Trezor fall back to a more detailed, generic confirmation screen whenever a lockup is present, so the user can see and approve the terms explicitly.
Security candidatechore(vendor): update secp256k1-zkp to v0.7.1by M1nd3r · 0904b41b · Aug 11, 2026 · 1 fileMessage 88 · StrongInformational 15Details
Commit message · M1nd3r
chore(vendor): update secp256k1-zkp to v0.7.1
- Updated from v0.7.0. - Pinned to release/commit: https://github.com/bitcoin-core/secp256k1/releases/tag/v0.7.1 - Changelog: https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md#071---2026-01-26 - Changes: https://github.com/bitcoin-core/secp256k1/compare/v0.7.0...v0.7.1
88/100 · StrongMessage clarity
✓ 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
cryptography-sensitive path
AI analysis · Informational 15/100
This commit only updates a bundled cryptographic library (secp256k1-zkp) from version 0.7.0 to 0.7.1. The actual code change is a one-line update to the submodule pointer. The commit message does not describe any security fix, and no security-relevant details are visible in the diff itself.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
access control
AI analysis · Informational 15/100
This commit removes a single line from the project's Git submodule configuration. It stops pinning the libtropic submodule to the 'develop' branch, meaning the project will now use the submodule's default branch (likely 'main' or 'master'). There is no code change, no bug fix, and no direct security issue visible in the diff itself.
Security candidatechore(core/embed): clear temporary buffer across Optiga/Tropic callsby Roman Zeyde · 01ebda93 · Aug 10, 2026 · 1 fileMessage 70 · AdequateLow 37Details
Commit message · Roman Zeyde
chore(core/embed): clear temporary buffer across Optiga/Tropic calls
We don't need to keep Optiga/Tropic-generated entropy after XOR-ing it into `dest`.
In addition, it prevents the "Tropic" for-loop from "undoing" the "Optiga" for-loop result, if `tropic_random_buffer()` somehow succeeds without modifying its buffer.
The additional `memzero` calls performance impact should be small compared to Optiga/Tropic communication latency.
[no changelog]
70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly! Contains work-in-progress language
Why it was queued
entropy or randomnessseed or entropy path
AI analysis · Low 37/100
This is a hardening change for the random number generator inside Trezor hardware wallets. It makes sure that temporary memory holding secret random values from the Optiga and Tropic security chips is wiped immediately after use, rather than only once at the end. It also fixes a subtle edge case where a buggy Tropic chip call could leave old Optiga randomness in the temporary buffer, potentially weakening the final random output.
- implement FirmwareUI::select_menu - not used in flows yet
[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 commit adds a new Rust-based on-screen menu component for the Trezor hardware wallet's Bolt user interface. It is a straightforward feature implementation and does not fix or introduce any obvious security issue. The component is not yet wired into any user-facing flows.
AI review queuedfeat(nfc): Update RFAL library to version 4.2.0 due to added presence check on ISO-DEP layerby Ludek Farsky · 6e2dbb91 · Aug 10, 2026 · 62 filesMessage 74 · AdequateLow 32Details
Commit message · Ludek Farsky
feat(nfc): Update RFAL library to version 4.2.0 due to added presence check on ISO-DEP layer
[no changelog]
74/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
second-pass: unusually broad change
AI analysis · Low 32/100
This commit upgrades the third-party STMicroelectronics NFC middleware (RFAL) inside Trezor firmware from version 4.0.2 to 4.2.0. The stated reason is to add a 'presence check' in the ISO-DEP layer, which helps the device verify that an NFC card is still nearby during a transaction. The diff is almost entirely a bulk import of ST's updated library files, so the actual security-relevant changes are not visible in the commit itself. There is no Trezor changelog entry and no CVE or advisory referenced.
Security candidatefeat(common/protobuf): integrate EIP-7702 delegation into `EthereumSignTxEIP1559`by Roman Zeyde · b0932cd4 · Aug 8, 2026 · 5 filesMessage 62 · AdequateInformational 14Details
Commit message · Roman Zeyde
feat(common/protobuf): integrate EIP-7702 delegation into `EthereumSignTxEIP1559`
[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 14/100
This commit only changes the data format definitions (protobuf messages) used to talk to a Trezor hardware wallet. It adds new optional fields for an upcoming Ethereum feature called EIP-7702, which lets an account temporarily act like a smart contract. The commit does not contain any actual signing logic, user confirmation screens, or security checks. Because it is just a protocol definition update, it does not by itself create a vulnerability, but it is a building block for future code that will handle these authorizations.
Security candidatetest(core/ethereum): EIP-7702 tuple nonce must be non-zeroby Roman Zeyde · 76cd2ed4 · Aug 8, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · Roman Zeyde
test(core/ethereum): EIP-7702 tuple nonce must be non-zero
[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 or wallet pathauthentication path
AI analysis · Informational 15/100
This commit only changes test data and expected screen fingerprints for Trezor's Ethereum EIP-7702 signing tests. It replaces one test case that used a nonce of 0 with the same scenario using a nonce of 67, because the real-world protocol rule requires the tuple nonce to be non-zero. No production firmware code is modified, so this commit does not fix or introduce a security vulnerability in shipped devices.
AI review queuedtest(core): drop an unused parameter of `make_payment_request()`by Roman Zeyde · 6dd19fdc · Aug 8, 2026 · 8 filesMessage 72 · AdequateInformational 15Details
Commit message · Roman Zeyde
test(core): drop an unused parameter of `make_payment_request()`
[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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only cleans up test code by removing an unused 'session' argument from a helper function used in automated tests. It does not change the actual Trezor firmware or any code that runs on the device, so it has no security impact for users.
Thread a per-chunk progress callback through upload_image/smp_upload_app_image; add nrf_update_with_progress (nrf_update delegates with NULL, so the coreapp syscall ABI is unchanged).
[no changelog]
Co-Authored-By: Claude Opus 4.8 <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 15/100
This commit adds a progress bar feature for firmware updates sent to the nRF wireless chip inside Trezor devices. It threads a callback function through the upload code so the bootloader can show how much of the image has been transferred. The existing public syscall entry point is deliberately left unchanged, so normal app behavior is unaffected. There is no security fix or vulnerability here.
Security candidatedocs(core): document rng_fill_buffer_strong_time()by Andrew Kozlik · c5687f76 · Aug 7, 2026 · 1 fileMessage 67 · AdequateInformational 15Details
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
67/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
entropy or randomnessseed or entropy path
AI analysis · Informational 15/100
This commit only adds a plain-English comment explaining an existing function that estimates how long a random-number generation call takes. No code behavior changed, and nothing was fixed or added that affects security.
Security candidatechore: guard against insecure PRNG in bare-metal buildby Andrew Kozlik · 4f8f4586 · Aug 7, 2026 · 1 fileMessage 77 · AdequateLow 44Details
Commit message · Andrew Kozlik
chore: guard against insecure PRNG in bare-metal build
[no changelog]
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
entropy or randomnesscryptography-sensitive path
AI analysis · Low 44/100
This commit adds compile-time guards to prevent an intentionally insecure random-number generator from being accidentally included in firmware that runs directly on Trezor hardware. It does not fix an active bug, but it adds safety rails so a future build misconfiguration cannot silently ship weak randomness to real devices.
Security candidatebuild(core/io): move headers to the right placeby matejcik · cf3597e9 · Aug 7, 2026 · 4 filesMessage 57 · ThinInformational 15Details
Commit message · matejcik
build(core/io): move headers to the right place
after smp had been moved to io crate
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100
This commit is a routine build cleanup. It moves a header file to the correct folder and updates two source files to include it from the new location. There is no security-relevant change here.
AI review queuedbuild(core): drop stale trezor_lib dependency from kernelby matejcik · 7e64fef5 · Aug 7, 2026 · 3 filesMessage 62 · AdequateInformational 12Details
Commit message · matejcik
build(core): drop stale trezor_lib dependency from kernel
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
second-pass: broader security terminology
AI analysis · Informational 12/100
This is a routine build cleanup in the Trezor firmware kernel. It removes an unused Rust library dependency called 'trezor_lib' and replaces it with a reference to another module ('io') to ensure certain Rust symbols are still included during linking. There is no indication this change fixes or introduces a security vulnerability.
Security candidatefeat(core/rust): move nrf and smp out of trezor_libby matejcik · 53761741 · Aug 7, 2026 · 31 filesMessage 77 · AdequateInformational 15Details
Commit message · matejcik
feat(core/rust): move nrf and smp out of trezor_lib
* moves irq to sys::irq * moves from_c_str and from_c_array to rtl::util * moves smp and trezorhal::nrf to io
77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100
This commit is a straightforward internal code reorganization. It moves several low-level hardware communication modules (NRF radio, SMP firmware-update protocol, IRQ utilities, and C-string helpers) into different Rust crates so the project structure is cleaner. No security vulnerability is introduced or fixed; it is purely a refactoring change.
build(core): propagate emulator feature from projects
left out: * firmware, which removes emulator feature instead * kernel, whose dep on trezor_lib will be removed in a followup PR
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 · Informational 15/100
This commit is a build-system cleanup for the Trezor firmware's Rust code. It changes how the 'emulator' feature flag is passed between different software components. The firmware project no longer supports the emulator feature (which makes sense because real firmware runs on hardware, not an emulator), while the bootloader, prodtest, and core Rust library now propagate the feature more consistently. There is no indication of a security vulnerability in this change.
fix(emulator): initialize mono counters before running bootemu
[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 35/100
This commit fixes how the Trezor emulator initializes its 'monotonic counters'—security counters that only ever increase and are used to prevent downgrades to older, possibly vulnerable firmware. Before this fix, the emulator did not explicitly initialize these counters before running the boot emulator, which could lead to uninitialized or incorrect counter values during emulator-based testing. The fix adds a dedicated initialization routine and calls it in every relevant firmware component. On real hardware the initialization is currently a no-op, so this primarily affects the Unix/emulator build used for development and testing.
fix(crypto): make aes functions reject negative length
[no changelog]
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Low 47/100
This commit fixes a bug in Trezor's AES encryption/decryption code where a negative length value could be passed to low-level AES functions. Previously, those functions treated the signed length as a large unsigned number, which could cause them to read or write far beyond the intended memory buffer. The patch makes every AES mode reject negative lengths and adds error handling so callers fail safely instead of silently producing bad results or touching memory they shouldn't.