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 queuedfix(core/ethereum): disallow non-zero ETH value on SLIP-24 ERC-20 swapsby Roman Zeyde · eefd32c3 · Aug 21, 2026 · 3 filesMessage 77 · AdequateHigh 70Details
Commit message · Roman Zeyde
fix(core/ethereum): disallow non-zero ETH value on SLIP-24 ERC-20 swaps
(cherry picked from commit 2c769ec0f61026d3472f5d2d261bf0ed043ab5c9)
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 pathsecond-pass: security-sensitive path
AI analysis · High 70/100
This update fixes a logic flaw in Trezor's Ethereum signing code. When a user was doing an ERC-20 token swap using a SLIP-24 payment request, the device could also be instructed to send native ETH at the same time. That combination is not expected in a normal token swap and could let an attacker trick the user into authorizing an unintended ETH transfer alongside the token swap. The fix now rejects such transactions outright.
AI review queuedtest(core/ethereum): fix SLIP-24 payment request for ERC-20 tokensby Roman Zeyde · 3d24462d · Aug 21, 2026 · 2 filesMessage 72 · AdequateInformational 12Details
Commit message · Roman Zeyde
test(core/ethereum): fix SLIP-24 payment request for ERC-20 tokens
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 12/100
This commit only adds a new automated test case for signing an Ethereum ERC-20 token transfer using a SLIP-24 payment request. It does not change any production firmware code, so it cannot introduce a security vulnerability or directly fix one in shipped software. The change is purely in the test suite and its recorded expected screen outputs.
AI review queuedrefactor(core/ethereum): simplify `test_signtx_payment_req_long_value`by Roman Zeyde · 1e897557 · Aug 21, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
✓ 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 only refactors a single automated test file for Ethereum transaction signing on Trezor hardware wallets. It extracts duplicated code into a helper function and updates how the test checks for an expected error message. There is no change to the actual firmware, wallet logic, or security behavior.
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.
AI review queuedfix(l10n): fix German recover button textby Michal Kazda · d975b58f · Aug 20, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda
fix(l10n): fix German recover button text [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 German translation update. It changes the wording on a wallet recovery button and refreshes the translation signature file that verifies the translations are authentic. There is no security issue here.
AI review queuedfix(core): limit protobuf nesting depthby Martin Milata · dd7afbc3 · Aug 20, 2026 · 3 filesMessage 57 · ThinModerate 66Details
Commit message · Martin Milata
fix(core): limit protobuf nesting depth
[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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Moderate 66/100
This commit adds a hard limit on how deeply nested Protobuf messages can be when the Trezor device decodes them. Without such a limit, a malicious or malformed message could nest messages inside messages indefinitely, potentially crashing the device or causing other problems. The change caps nesting at 16 levels and adds a test to confirm that deeper nesting is rejected.
AI review queuedrefactor(python): faster serialization of nested protobufby Martin Milata · 83947a18 · Aug 20, 2026 · 1 fileMessage 77 · AdequateInformational 18Details
Commit message · Martin Milata
refactor(python): faster serialization of nested protobuf
The function was exponential in the nesting depth. Changed to use more memory while not blowing up CPU.
[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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This is a routine performance refactor in Trezor's Python library. It replaces a slow, CPU-heavy way of measuring nested protobuf message sizes with a faster approach that builds the message in memory once. There is no indication this fixes a security vulnerability; it is described purely as a speed improvement.
AI review queuedstyle(core/rust): clippyby matejcik · 6f96a4d4 · Aug 20, 2026 · 8 filesMessage 28 · OpaqueInformational 15Details
Commit message · matejcik
style(core/rust): clippy
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine code cleanup to satisfy the Rust Clippy linter. It removes unnecessary reference symbols (&), rewrites a small match block to assign a value directly, and removes an unused import. There is no functional change and no security relevance visible in the diff.
✓ 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.
Security candidatefix(core): assert the monotonic versions fit what monoctr can storeby tychovrahe · 4156e6aa · Aug 20, 2026 · 1 fileMessage 85 · StrongLow 34Details
Commit message · tychovrahe
fix(core): assert the monotonic versions fit what monoctr can store
monoctr stores its counters UNARY -- value N is N written 16-byte blocks -- so the encoding, not the uint8_t the value travels in, is what caps them at MONOCTR_MAX_VALUE (63). A model that raises a monotonic version past that gets no build error; it fails later, at runtime, and confusingly:
* the boardloader compares the boot header against the stored floor, cannot write the new value, and reports "BOOTLOADER DOWNGRADED" on a perfectly good image; * the firmware and secmon floors silently stop advancing, so anti-rollback quietly weakens instead of failing.
Assert all three at build time instead. Every model is well inside the limit today (highest is 3), so this only fixes the failure mode of a future bump.
version_check.c is the only place all three can be checked. The firmware and secmon values reach their images through header.S, where _Static_assert cannot go, and model_version.h is itself pulled into that assembly via version.h, so the checks cannot live there either. This translation unit both sees all three constants and owns the monoctr policy they feed.
SECMON_MONOTONIC_VERSION is guarded: only models with a secmon define it (4 of 9 today).
Verified by temporarily setting a model to 64 and confirming the build stops, and by building models with and without a secmon so both sides of the #ifdef compile.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
[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 · Low 34/100
This commit adds build-time safety checks to prevent future Trezor firmware versions from accidentally setting anti-rollback version numbers too high for the hardware storage to handle. If a version were set above the storage limit, the device could either wrongly refuse to boot a valid update, or silently stop enforcing downgrade protection. The fix prevents that mistake at compile time, before any device is shipped. It does not fix an active bug today because all current models are well below the limit.
Security candidatefeat(core/prodtest): Add pin padding to AUTHENTICATE and SET_PIN command.by kopecdav · 2beb4b17 · Aug 20, 2026 · 1 fileMessage 62 · AdequateLow 44Details
Commit message · kopecdav
feat(core/prodtest): Add pin padding to AUTHENTICATE and SET_PIN command.
[no changelog]
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
access control
AI analysis · Low 44/100
This commit changes a Trezor factory-testing tool (prodtest) so that PINs sent during NFC backup authentication and PIN setup are padded to a fixed length and encrypted with the Noise XXpsk3 protocol before being transmitted. Previously, the raw PIN was placed directly into the NFC APDU command. The change reduces the risk that someone sniffing NFC traffic could learn the PIN length or the PIN itself in plaintext. It is a defensive hardening improvement in a manufacturing/debug utility, not a fix for an active exploit in end-user firmware.
AI review queuedfix(solana): correct misleading account labels in token instruction UIby Jakub Janků · 5a424238 · Aug 19, 2026 · 4 filesMessage 93 · StrongModerate 53Details
Commit message · Jakub Janků
fix(solana): correct misleading account labels in token instruction UI
Fix wrong role labels in the SPL Token / Token 2022 UI definitions (the classic Token Program declares identical account lists):
- Burn: "Mint authority" -> "Owner" (the account is the owner/delegate) https://docs.rs/spl-token-2022-interface/3.1.1/spl_token_2022_interface/instruction/enum.TokenInstruction.html#variant.Burn - Freeze/Thaw Account: "Owner" -> "Freeze authority" https://docs.rs/spl-token-2022-interface/3.1.1/spl_token_2022_interface/instruction/enum.TokenInstruction.html#variant.FreezeAccount - Mint to Checked: "Owner" -> "Mint authority" https://docs.rs/spl-token-2022-interface/3.1.1/spl_token_2022_interface/instruction/enum.TokenInstruction.html#variant.MintToChecked - Revoke: "Revoke delegate" -> "Revoke delegate for" (the shown account is the source token account, not the delegate); also fix "Rewoke" typo https://docs.rs/spl-token-2022-interface/3.1.1/spl_token_2022_interface/instruction/enum.TokenInstruction.html#variant.Revoke
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> (cherry picked from commit e38b1ac28b1ebef85166360c3e1db1192d4b0699)
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 53/100
This commit fixes incorrect on-screen labels shown to Trezor users when they confirm Solana token operations such as burning tokens, freezing accounts, minting tokens, or revoking a delegate. The labels wrongly described whose account or authority was involved, which could trick a user into approving a transaction they did not understand. The actual blockchain instructions and account handling were not changed—only the text the user sees on the device screen.
✓ 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 · Moderate 51/100
This commit adds several missing safety checks in low-level hardware code for the Trezor hardware wallet. It prevents reading past the end of a too-short firmware image, avoids odd behavior when asked to read or write zero SD card blocks, ensures a signature buffer is large enough before use, and fixes a debug-message routine that could truncate or mishandle strings. These are defensive fixes; the commit message does not call them security fixes, but missing length checks in embedded code can sometimes be exploited to crash the device or leak nearby memory.
AI review queuedtest(solana): predefined staking flow classifiersby Jakub Janků · 1422a017 · Aug 19, 2026 · 2 filesMessage 82 · StrongInformational 15Details
Commit message · Jakub Janků
test(solana): predefined staking flow classifiers
[no changelog]
(cherry picked from commit 21cc27648ce794817622bb2207ee520d5d5fad38)
82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds automated tests for Solana staking transaction detection. It does not change any production wallet code, so it cannot directly introduce a security vulnerability or fix one in shipped firmware.
AI review queuedrefactor(solana): separate staking tx format check from confirmationby Jakub Janků · 012f9768 · Aug 19, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · Jakub Janků
refactor(solana): separate staking tx format check from confirmation
This will allow us to unit test the decision mechanism that switches between the predefined and the generic confirmation flow.
Token transfer code is structured in a similar way.
[no changelog]
(cherry picked from commit 17297513cf54f8c286df02ce81ba510c8a354df6)
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a code cleanup for Trezor's Solana staking transaction handling. It splits one large function into smaller helper functions that decide whether a transaction should use a simplified, user-friendly confirmation screen. The actual security checks and confirmation behavior are unchanged; the change only makes the code easier to test.
Security candidatechore(python): generate CoSi nonces randomly by defaultby M1nd3r · 114f6e2f · Aug 19, 2026 · 7 filesMessage 85 · StrongModerate 60Details
Commit message · M1nd3r
chore(python): generate CoSi nonces randomly by default
- Deterministic nonce derivation is persisted, it is safe for publicly known keys only. It is used for reproducible CoSi signing with dev keys.
[no changelog]
(cherry picked from commit 65fa3edbf020dc1fe356a905b944da92a1b55766)
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 boundary
AI analysis · Moderate 60/100
This commit changes the Trezor Python library's collective signing (CoSi) helper so that, by default, it generates random nonces instead of deriving them deterministically from the private key and message. The old deterministic mode is kept only for publicly known development keys, because using it with real secret keys is dangerous: a malicious coordinator could trick the same key into signing the same message twice with different combined nonces, which would leak the private key. The patch itself is a security improvement, not an exploit, but it fixes a latent vulnerability in the library's API design.
- reinterpret the definitions magic `trzd1` as magic + version, i.e. `trzd` + `1` - this allows us to release backwards incompatible definitions with a bumped version - this is a necessary preparation for a signature quorum change
[no changelog]
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
signing boundary
AI analysis · Informational 23/100
This commit refactors how Trezor firmware recognizes external 'definitions' files (the data blobs that describe Ethereum networks and tokens). It splits the old 5-byte header 'trzd1' into a 4-byte magic 'trzd' plus a 1-byte version number. The change is framed by the authors as a necessary preparation for a future signature-quorum change, not as a fix for an active vulnerability. No currently reachable security flaw is present in the diff; the code still only accepts version '1', which keeps the existing 2-of-3 signature requirement.
AI review queuedfix(solana): avoid re-confirmation in staking flowsby Jakub Janků · c195cec9 · Aug 19, 2026 · 1 fileMessage 85 · StrongLow 35Details
Commit message · Jakub Janků
fix(solana): avoid re-confirmation in staking flows
Decide whether to use the predefined flow or whether to fall back to the generic flow before requesting any confirmation from the user.
[no changelog]
(cherry picked from commit 4d3b5a5a64ea0fcaf34934d9a61e3ee70eb06449)
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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 35/100
This change fixes a logic bug in how Trezor handles Solana staking transactions. Previously, the device could ask the user to confirm a staking detail before it had fully verified that the transaction matched a safe, predefined pattern. The fix moves that confirmation check to after all safety checks are complete, so the device only asks for confirmation when it is confident the transaction is a known, legitimate staking flow. This prevents a potentially malicious or malformed transaction from tricking the user into confirming something risky.
Security candidatefeat(ui,tron): support for native transfer with smart contract interactionby PrisionMike · f36dff00 · Aug 19, 2026 · 6 filesMessage 62 · AdequateLow 28Details
Commit message · PrisionMike
feat(ui,tron): support for native transfer with smart contract interaction
[no changelog]
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Low 28/100
This commit adds user-interface support for Tron smart-contract transactions that also move native TRX coins. Previously, the device screen did not show the native TRX amount when a smart contract was involved. Now it can display that amount so the user sees what they are really sending. The change is mostly UI wiring and test data; it does not appear to alter transaction validation or signing logic.
AI review queuedfeat(tron): core edits to include `call_value` in `TriggerSmartContract`by PrisionMike · f476eaec · Aug 19, 2026 · 3 filesMessage 62 · AdequateLow 44Details
Commit message · PrisionMike
feat(tron): core edits to include `call_value` in `TriggerSmartContract`
[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 · Low 44/100
This commit changes how Trezor hardware wallets handle Tron smart-contract calls that include native TRX tokens. Previously, the device did not display or validate the `call_value` field, which means a user could be tricked into sending TRX along with a contract call without seeing it on the device screen. The patch adds a safety check that rejects oversized values and shows the TRX amount during transaction confirmation. It is a defensive fix rather than an exploit.