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): fix SLIP-24 payment request for ERC-20 tokensby Roman Zeyde · b13a17f9 · Aug 19, 2026 · 2 filesMessage 62 · AdequateLow 38Details
Commit message · Roman Zeyde
fix(core/ethereum): fix SLIP-24 payment request for ERC-20 tokens
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 38/100
This commit fixes a bug in the Trezor hardware wallet's Ethereum transaction signing flow. When using SLIP-24 payment requests with ERC-20 token transfers, the device could incorrectly skip the user-confirmation step for the transaction details. The fix ensures that 'clear signing' mode (which bypasses some confirmations) is checked before the payment-request path, so users still see and approve the token transfer details.
AI review queuedchore(translations): sync additional Crowdin translationsby Michal Kazda · a2b756fb · Aug 19, 2026 · 6 filesMessage 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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only updates translated text strings in Czech, German, Spanish, French, and Portuguese translation files, plus the corresponding translation signature metadata. There are no code changes, no security fixes, and no behavior changes. It is a routine localization sync.
AI review queuedfix(core): improve confirmation UX in super-shamirby obrusvit · c97383ba · Aug 19, 2026 · 14 filesMessage 77 · AdequateInformational 15Details
Commit message · obrusvit
fix(core): improve confirmation UX in super-shamir
- confirm groups setup - confirm individial group thresholds
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 · Informational 15/100
This commit improves the on-screen confirmation experience when creating an advanced Shamir backup on a Trezor device. It adds extra prompts that show the user how many backup groups exist, how many groups are needed to recover the wallet, and the threshold for each individual group. There is no security vulnerability here; it is purely a user-interface improvement to help people verify their backup settings.
AI review queuedchore(translations): sync Crowdin translationsby Thalarion · 883edebe · Aug 19, 2026 · 6 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion
chore(translations): sync Crowdin translations
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine translation update for the Trezor hardware wallet firmware. It only changes user-facing text strings in Czech, German, Spanish, French, and Portuguese translation files, plus the translation signature metadata. There are no code logic changes, no security fixes, and no functional changes to how the device operates.
feat(legacy,core): add make.me.blink U2F dummy app ID
Show "not registered" message instead of a registration prompt when Firefox sends its dummy U2F register request.
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 pathauthentication path
AI analysis · Informational 21/100
This commit is a small user-experience fix, not a security patch. Firefox's U2F support sends a special dummy registration request to check whether a security key is present. Trezor previously recognized two such dummy IDs, but Firefox's newer authenticator code uses a third one ('make.me.blink'). Without this change, Trezor would prompt the user to register the device, which is confusing. The fix makes Trezor show a simple 'not registered / already registered' message instead. It does not fix a vulnerability that lets an attacker steal funds or bypass protection.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This is a simple code cleanup: the developer removed a local alias named NOISE_TAG_SIZE_BYTES and replaced every use of it with the existing official constant NOISE_XXPSK3_TAG_SIZE. The numeric value and behavior of the code are unchanged, so there is no security impact.
Security candidatechore(crypto): add checks to noiseby M1nd3r · c59f833b · Aug 18, 2026 · 5 filesMessage 72 · AdequateModerate 59Details
Commit message · M1nd3r
chore(crypto): add checks to noise
- Check max message size. - Respect aes-gcm block limits.
[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
cryptography-sensitive path
AI analysis · Moderate 59/100
This commit hardens the Noise protocol code used in Trezor firmware by adding size limits and nonce limits to prevent two cryptographic problems: encrypting or decrypting messages that are too large for the protocol, and reusing the same encryption nonce after the counter wraps around. Reusing a nonce with AES-GCM can destroy the confidentiality of messages and allow attackers to forge fake messages. The patch also wipes sensitive context data more thoroughly when errors occur, reducing the chance that leftover key material could leak.
AI review queuedrefactor(translations): remove unused stellar_timeboundsby Jakub Janků · 725b3eb0 · Aug 18, 2026 · 10 filesMessage 77 · AdequateInformational 15Details
(cherry picked from commit f4ad393ee8c8ec03a73ff89e23adec48e77dbbc5)
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 · Informational 15/100
This commit removes an unused translation string called 'stellar__timebounds' from the Trezor firmware's translation system. It is a cleanup/refactoring change with no visible effect on device behavior or security. The signatures.json file was also updated because removing a string changes the cryptographic hash (merkle root) used to verify translation files.
Security candidatefeat(stellar): show network in signing flowsby Jakub Janků · 7e4bbee9 · Aug 18, 2026 · 9 filesMessage 93 · StrongLow 30Details
Commit message · Jakub Janků
feat(stellar): show network in signing flows
The network can be optionally viewed in the info menu on the last screen of the tx and auth entry signing flows.
The network was intentionally omitted from the confirmation flow during a recent redesign: https://github.com/trezor/trezor-firmware/issues/5148#issuecomment-2975448688
However, the stated rationale somewhat overlooked users that wish to interact with multiple networks. For users that have accounts both on mainnet and testnet, it is crucial to be able to distinguish that they don't sign a transaction for mainnet that was actually meant to be sent to testnet only.
Fixes: https://github.com/satoshilabs/trezor-firmware/issues/319 (cherry picked from commit cb97b0b37cccfa60619111ebc35aad518635d5b3)
93/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✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarycryptography-sensitive pathsigning or wallet pathauthentication path
AI analysis · Low 30/100
This commit improves the Stellar signing experience on Trezor hardware wallets by letting users see which network (Mainnet, Testnet, or Futurenet) a transaction is for before approving it. Previously, the network was intentionally hidden from the main confirmation flow after a redesign, which could lead someone with accounts on both mainnet and testnet to accidentally approve a mainnet transaction they only intended for testnet. The fix adds the network name to an info menu on the final review screen for both regular Stellar transactions and Soroban authorizations. It also adds support for the Stellar Futurenet network passphrase. This is a security/usability improvement rather than a remote-exploitable vulnerability.
Security candidatefeat(bolt): increase item limit in show_info_with_cancelby Jakub Janků · 063b3f2a · Aug 18, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · Jakub Janků
feat(bolt): increase item limit in show_info_with_cancel
One info item occupies 2 paragraphs; the limit is therefore increased from 4 to 18 items.
This is a preparatory commit.
[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
boot or update path
AI analysis · Informational 15/100
This commit changes the on-screen display component used by one user-interface helper from a short paragraph container to a long one, raising the maximum number of info lines that can be shown from 4 to 18. The commit message explicitly calls it a 'preparatory commit' and there is no indication of a security bug or fix.
Security candidatefix(caesar): don't omit description in confirm_valueby Jakub Janků · c9c2d315 · Aug 18, 2026 · 3 filesMessage 85 · StrongModerate 51Details
Commit message · Jakub Janků
fix(caesar): don't omit description in confirm_value
... when info_items is non-empty.
This fixes an issue in Ripple confirm_account_deletion where the fee limit is shown without any description and multiple similar issues in Stellar payment-like operations (which internally use confirm_stellar_output_amount).
[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 · Moderate 51/100
This commit fixes a display bug in Trezor hardware wallets running the 'Caesar' user interface. In certain Ripple and Stellar transaction confirmation screens, a helpful description label (for example, explaining that a shown number is a fee limit or payment amount) was accidentally left off. The fix makes sure the description appears alongside the value, so users are less likely to misread what they are approving. It is a user-interface clarity issue rather than a direct theft-of-funds vulnerability, but it could contribute to a user approving a transaction they do not fully understand.
AI review queuedfix(l10n): add generated filesby Michal Kazda · 107d49e1 · Aug 18, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda
fix(l10n): add generated files [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 · Informational 15/100
This commit only regenerates translation files after some text labels were moved from one category to another (for example, 'Authenticate' and 'Wipe' were changed from general words to button labels). There is no code behavior change, no bug fix, and no security relevance visible in the diff.
Security candidatefix(l10n): change words__ into buttons__ in codeby Michal Kazda · ccf540df · Aug 18, 2026 · 11 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda
fix(l10n): change words__ into buttons__ in code [no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a straightforward internal cleanup of translation key names. It changes labels like 'words__continue_anyway' to 'buttons__continue_anyway' in code that displays on-screen buttons and menu items. The actual user-facing text shown on the device is unchanged; only the internal identifier used to look up that text was renamed. There is no security-relevant change.
AI review queuedfix(ripple): show dt even when it's 0by PrisionMike · 76faf52f · Aug 18, 2026 · 4 filesMessage 57 · ThinLow 49Details
Commit message · PrisionMike
fix(ripple): show dt even when it's 0
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 · Low 49/100
This commit fixes a bug in Trezor's Ripple (XRP) signing code. When a payment request included a destination tag of 0, the device treated it as if no tag was set, so it did not show or verify the tag. Because destination tags are used to route funds to the correct recipient on exchanges, omitting tag 0 could let an attacker trick a user into approving a payment that looks tagless but actually sends to tag 0, potentially sending funds to the wrong account or making them hard to recover.
AI review queuedfix(core/monero): validate change address on sweep transactionsby Petr Susil · 11c2dedf · Aug 18, 2026 · 3 filesMessage 100 · StrongHigh 74Details
Commit message · Petr Susil
fix(core/monero): validate change address on sweep transactions
The sweep shape (declared change amount 0, two outputs) is exempt from the change ownership check, because on a sweep the change address is a random throwaway address, not ours. But the shape is host-controlled, so a malicious host can point change_dts.addr at the paying recipient and have the exemption accept it. That output is then keyed as change in step 6, derived from our own view key (a*R), leaving it unspendable by both the recipient and the owner.
Reject the aliasing: an address we decline to validate must never be the address of an output that carries money. Honest sweeps are unaffected -- their fake output carries amount 0.
Fixes: https://github.com/trezor/trezor-firmware/issues/7544 (cherry picked from commit ea6caf1e1875df05e983629df90d3dd217af4ab9)
100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · High 74/100
This update fixes a bug in how Trezor handles certain Monero 'sweep' transactions. In a sweep, one output is a fake zero-value decoy with a random address, and the device normally skips checking that the change address belongs to the wallet. A malicious computer app could exploit that skip by claiming the real payment recipient's address is the change address. The device would then encrypt the recipient's output using the wallet's own secret view key, making the money effectively unspendable by the recipient and unrecoverable by the sender. The fix adds a check: if the unvalidated change address appears on any output that actually carries money, the transaction is rejected. Honest sweeps, where the decoy carries zero coins, still work normally.
Security candidatefeat(core): support "dangerous" hold-to-confirm on Deliziaby Roman Zeyde · 31a076a8 · Aug 17, 2026 · 3 filesMessage 62 · AdequateInformational 20Details
Commit message · Roman Zeyde
feat(core): support "dangerous" hold-to-confirm on Delizia
[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 20/100
This commit adds a new user-interface option for the Trezor Safe 5 (Delizia) that lets certain confirmation screens use a red 'danger' hold-to-confirm style instead of the normal green one. It is purely a visual/theming change and does not alter what the device signs, what it allows, or any security policy. The large diff is mostly updated test screenshot hashes caused by the changed colors/text.
Security candidatechore(core): move `trezor.crypto.cosi` module to unittestsby Roman Zeyde · 2af21738 · Aug 17, 2026 · 4 filesMessage 77 · AdequateInformational 15Details
Commit message · Roman Zeyde
chore(core): move `trezor.crypto.cosi` module to unittests
It's no longer used in firmware.
[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
cryptography-sensitive path
AI analysis · Informational 15/100
This commit removes an unused cryptography helper module from the actual Trezor firmware and keeps it only in the test suite. There is no security bug being fixed here; it is a routine cleanup to avoid shipping dead code.
Security candidatechore(core/tools): drop bootloader_hashes for boot_ucb modelsby tychovrahe · c5a23c8e · Aug 17, 2026 · 7 filesMessage 100 · StrongInformational 15Details
Commit message · tychovrahe
chore(core/tools): drop bootloader_hashes for boot_ucb models
UCB models verify a staged bootloader through its PQ boot-header signature (boot_image_replace under USE_BOOT_UCB), not through the padded blake2s digests in bootloader_hashes.h -- boot_image_embdata.c only wires .hash_00/.hash_FF `#ifndef USE_BOOT_UCB`, and that file is compiled only by the firmware project, which enables boot_ucb for these models. The digests are therefore never referenced for UCB models; the generated header only churned whenever the bootloader binary changed, for no consumer.
Skip generation for boot_ucb models (detected from the model.toml features list), remove the now-dead #include from their model headers, and delete the stale generated files for T3W1, D002 and T3T2.
[no changelog]
Co-Authored-By: Claude Opus 4.8 <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✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryupdate trustboot or update path
AI analysis · Informational 15/100
This is a cleanup change that stops generating unused bootloader hash files for newer Trezor models (D002, T3T2, T3W1). These models already verify the bootloader using a different mechanism (UCB with post-quantum signatures), so the old hash files were never actually used. The commit deletes the stale files and removes their #include references. There is no security vulnerability here.
Security candidatefix(stellar,python): use -p for --network-passphraseby Jakub Janků · 2f2ab1f7 · Aug 16, 2026 · 1 fileMessage 90 · StrongInformational 20Details
Commit message · Jakub Janků
fix(stellar,python): use -p for --network-passphrase
Previously, -n was used which collided with -n for --address. The short name -p is used in the sign-soroban-authorization command for the corresponding option with the same effect.
[no changelog]
90/100 · StrongMessage 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
Why it was queued
access control
AI analysis · Informational 20/100
This is a tiny command-line interface (CLI) fix for the Stellar-related commands in Trezor's Python library. Two different options were accidentally using the same short flag '-n': one for '--address' and one for '--network-passphrase'. The patch changes '--network-passphrase' to use '-p' instead, matching another Stellar command. This is mainly a usability bug, not a direct security vulnerability, because users could not reliably select the intended option by short flag.
Security candidatefeat(core): support dev-signed definitions on non-production buildsby Roman Zeyde · 3006c023 · Aug 16, 2026 · 12 filesMessage 85 · StrongInformational 19Details
Commit message · Roman Zeyde
feat(core): support dev-signed definitions on non-production builds
Similar to how dev-signed translations are supported via the `dev_keys` feature.
Definitions public keys are moved to `core/embed/rust/src/definitions/constants.rs`.
[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
boot or update path
AI analysis · Informational 19/100
This commit moves the public keys used to verify coin/token definitions from Python code into a new Rust module. It also makes development-signed definitions accepted on non-production builds, similar to an existing feature for translations. The change is a build/configuration refactor rather than a fix for an active security flaw. Production firmware still requires production signatures; dev keys are only accepted when the `dev_keys` feature is enabled, which is intended for development builds.
AI review queuedfix(core): update fixturesby Michal Kazda · b30af88e · Aug 16, 2026 · 2 filesMessage 47 · ThinInformational 12Details
Commit message · Michal Kazda
fix(core): update fixtures [no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 12/100
This commit only refreshes test data files: it updates a translation signature metadata file and regenerates UI test fixtures. There is no code change, no security fix, and no indication of a vulnerability being addressed.
AI review queuedrefactor(translations): merge {cardano,ethereum}__networkby Jakub Janků · b0a549cd · Aug 16, 2026 · 13 filesMessage 77 · AdequateInformational 15Details
This is a preparatory commit, the string will be used for another cryptocurrency as well.
[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 pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a harmless internal cleanup: the word "Network" was previously stored separately for Cardano and Ethereum, and is now merged into a single shared translation key called words__network. No user-facing text, security behavior, or transaction logic changed.
Security candidatefix(legacy): hardening ETH unstake and claimby obrusvit · b41173f3 · Aug 16, 2026 · 4 filesMessage 92 · StrongHigh 70Details
Commit message · obrusvit
fix(legacy): hardening ETH unstake and claim
- unlike stake, the value of unstake and claim is supplied as a contract arg. Even though the contracts are non-payable, we must enforce `msg.value` to be 0 - in addition, enforce the right chain_id to prevent replay attacks
(cherry picked from commit f0cd25f93bde76a0f71d0b47ec1907484b0abeba)
92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
explicit security languagedefensive validationboot or update path
AI analysis · High 70/100
This update fixes a security flaw in Trezor's older hardware wallet firmware for Ethereum staking operations. Previously, when a user tried to 'unstake' or 'claim' staked ETH, the device did not reliably block ETH from being sent along with the transaction (msg.value), even though those smart-contract functions are not supposed to accept money. It also did not strictly check that the transaction was on the correct Ethereum network (chain ID), which could have allowed a malicious or accidental transaction on one network to be replayed on another. The fix enforces zero ETH value for unstake/claim and ties each allowed contract address to its proper network.
Security candidatefix(core): hardening ETH unstake and claimby obrusvit · 72414778 · Aug 16, 2026 · 4 filesMessage 92 · StrongHigh 74Details
Commit message · obrusvit
fix(core): hardening ETH unstake and claim
- unlike stake, the value of unstake and claim is supplied as a contract arg. Even though the contracts are non-payable, we must enforce `msg.value` to be 0 - in addition, enforce the right chain_id to prevent replay attacks
(cherry picked from commit 31323e62fbae7bb7b9ccc17a236e97cd8efeb91a)
92/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
explicit security languagedefensive validationsigning or wallet path
AI analysis · High 74/100
This update tightens the rules for two Ethereum staking operations—unstake and claim—on Trezor hardware wallets. Before the fix, the device did not verify that the user was on the correct Ethereum network (chain ID) and did not block ETH from being attached to unstake/claim transactions. Because those contract functions reject incoming ETH, any ETH sent with them would normally be lost. The patch now rejects such transactions before they can be signed, preventing accidental or malicious loss of funds and cross-chain replay attacks.
AI review queuedchore(translations): sync Crowdin translationsby Thalarion · 82264593 · Aug 15, 2026 · 4 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion
chore(translations): sync Crowdin translations
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only updates translated text strings in Czech, German, and Spanish language files, plus the corresponding translation signature metadata. There are no code, logic, or security-related changes.