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 queuedtest: cover every multisig export point on coreby Petr Susil · e631873a · Sep 16, 2026 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · Petr Susil
test: cover every multisig export point on core
The tests skipped the Casa and Unchained account levels, and ran on Trezor One, which does not implement this behaviour. Add those paths under every script type a message can be signed with, and mark the tests core only.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds and adjusts automated tests for message signing on Trezor hardware wallets. It does not change any production firmware code, cryptographic behavior, or user-facing functionality. There is no security vulnerability here.
AI review queuedtest(solana): create account from a foreign baseby Jakub Janků · 2eb57298 · Sep 14, 2026 · 2 filesMessage 82 · StrongInformational 15Details
Commit message · Jakub Janků
test(solana): create account from a foreign base
[no changelog]
(cherry picked from commit 5b037becd0fd6306150fe2d99ec752e96a98223a)
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 a new test case for Solana transaction signing. It does not change any production firmware code, so it cannot directly introduce a security vulnerability. The test checks that the device can sign a 'create account with seed' transaction where the base account is different from the funding account (a 'foreign base').
refactor(core): improve internal representation of protobuf definitions
[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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 30/100
This commit is a code cleanup that changes how Trezor firmware internally labels 32-bit versus 64-bit integer fields in its protobuf handling. It does not add or remove security checks by itself, but it makes the type system more precise so that future integer-overflow mistakes are harder to introduce. The change is described by the author as a refactor with no changelog entry.
✓ 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 61/100
This commit fixes the way a Trezor hardware wallet's Rust code reads protobuf message field keys. Previously, if reading a field key failed, the decoder silently stopped and treated the message as complete. Now it explicitly checks whether data remains and reports an error if a malformed or truncated field key is encountered. The change prevents an attacker from sneaking invalid or truncated protobuf data past the parser, which could lead to messages being accepted even though they contain garbage or hidden fields.
AI review queuedfeat(solana): confirm space when creating accountsby Jakub Janků · 04ed8330 · Sep 11, 2026 · 4 filesMessage 85 · StrongLow 37Details
Commit message · Jakub Janků
feat(solana): confirm space when creating accounts
We already let the user confirm the space parameter of the Allocate (With Seed) instruction. For consistency, do the same for the Create Account (With Seed) instruction.
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 37/100
This commit adds an on-screen confirmation step for the 'space' (data size) parameter when creating new Solana accounts on a Trezor device. Previously, this parameter was hidden from the user during Create Account instructions, even though it was already shown for a related 'Allocate' instruction. The change improves consistency and helps users spot transactions that request unexpectedly large storage allocations, which could be a sign of a malicious or misleading transaction.
AI review queuedfix(core): correct timestamp conversion in `time_gmtime2000()`by Roman Zeyde · d0f50b4d · Sep 9, 2026 · 4 filesMessage 95 · StrongLow 37Details
Commit message · Roman Zeyde
fix(core): correct timestamp conversion in `time_gmtime2000()`
It was working on the emulator (since `mp_int_t` is 64-bit) but failing on HW devices.
Also, improve `test_lock_time_datetime` coverage.
Note: `2106-02-07 06:28:15` = 2**32-1 seconds from epoch.
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 · Low 37/100
This commit fixes a date-handling bug in Trezor hardware wallets. The device converts Bitcoin transaction lock-time timestamps into human-readable dates on its screen. Before the fix, the code used a 32-bit signed integer on real hardware, so any date after the year 2038 (and in practice after about 2068 in this code) would be misread and the wrong date would be shown to the user. The fix switches to a 64-bit timestamp type and adds tests for far-future dates up to the year 2106. The main risk is that a user could be tricked into approving a transaction whose real lock-time date is different from what the device displays.
✓ 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 is a minor code cleanup in a test file. It reorganizes Python import statements to follow style guidelines by importing Callable and Sequence from collections.abc instead of typing. There is no functional change and no security relevance.
It better describes the reality as not only st-7789 controller is used inside the Trezor devices display panels.
[no changelog]
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
second-pass: unusually broad change
AI analysis · Informational 15/100
This commit is a simple rename of the display driver from 'st-7789' to 'i8080' because the code supports more than just the ST7789 display controller. It only changes file paths, feature names, and include guards. There is no change to how the code works, and no security issue is present.
AI review queuedfix(l10n): Indonesian fixes for Bolt/Caesar/Deliziaby Michal Kazda · f408bceb · Sep 4, 2026 · 2 filesMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda
fix(l10n): Indonesian fixes for Bolt/Caesar/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
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit updates Indonesian language translations for the Trezor hardware wallet. It adjusts wording and line breaks for different device models (Bolt, Caesar, Delizia, Eckhart) and updates the translation signature file. There are no code changes and no security implications.
AI review queuedchore(ci): add timeouts to all jobsby M1nd3r · 96de4ce3 · Sep 3, 2026 · 16 filesMessage 57 · ThinInformational 15Details
Commit message · M1nd3r
chore(ci): add timeouts to all jobs
[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 pathdocumentation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds time limits to automated GitHub Actions CI/CD jobs so they stop automatically if they run too long. It does not change any Trezor firmware code, wallet logic, cryptography, or user-facing behavior. There is no security vulnerability being fixed or introduced here.
AI review queuedrefactor(core): gate the power manager's RTC dependency on USE_RTCby tychovrahe · 9684ecd7 · Sep 2, 2026 · 1 fileMessage 100 · StrongInformational 15Details
Commit message · tychovrahe
refactor(core): gate the power manager's RTC dependency on USE_RTC
`power_manager_internal.h` included `<sys/rtc_scheduler.h>` unconditionally and declared `pm_driver_t.autohibernate_event_id` (an `rtc_event_id_t`) plus `pm_schedule_rtc_wakeup()` outside any guard, while every actual RTC user in the module is already `#ifdef USE_RTC`. The header therefore pulled the RTC scheduler interface into builds that never call it.
No functional change: with `USE_RTC` set the preprocessed output is identical, and with it unset no reference to the RTC scheduler remains.
Relevant because `rtc_schedule_wakeup_event()`/`rtc_cancel_wakeup_event()` are implemented only for stm32u5, so this is a prerequisite for building the `managed` policy anywhere else (e.g. a host unit test or an emulator built on an emulated PMIC).
[no changelog]
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100
This is a straightforward code cleanup: a header file now only includes real-time-clock (RTC) definitions when the feature is actually enabled. The commit explicitly states there is no functional change, and the diff shows only conditional compilation guards being added. There is no security issue here.
AI review queuedchore(core): sign translationsby Roman Zeyde · 2763e22f · Sep 1, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde
chore(core): sign translations
[no changelog]
(cherry picked from commit b40aaefea2cfea8128370809107fb6c56aaba0ec)
62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply adds a new digital signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. It is a routine metadata update with no code changes and no apparent security relevance.
AI review queuedfeat(core): report `Ethereum_EIP7702` from `GetFeatures`by Roman Zeyde · e4a7d054 · Sep 1, 2026 · 2 filesMessage 85 · StrongInformational 15Details
Commit message · Roman Zeyde
feat(core): report `Ethereum_EIP7702` from `GetFeatures`
1st part of https://github.com/trezor/trezor-firmware/issues/7693.
[no changelog]
85/100 · StrongMessage clarity
✓ Specific, 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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply advertises that Trezor Model T / Core devices support a new Ethereum feature called EIP-7702 when a host asks the device for its capabilities. It does not change how transactions are signed, authorized, or validated. There is no security-relevant behavior change.
AI review queuedfix(core): avoid panic on sentinel glyph lookupby obrusvit · 79d2aa73 · Aug 31, 2026 · 1 fileMessage 57 · ThinLow 37Details
Commit message · obrusvit
fix(core): avoid panic on sentinel glyph lookup
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
This commit fixes a bug in the Trezor firmware's translation system where looking up a special 'sentinel' (end-marker) value could cause the device to crash (panic). The fix changes the code to safely check whether the next entry exists before reading it, returning 'not found' instead of crashing. A test was added to confirm the sentinel lookup no longer panics.
AI review queuedrefactor(core): RIIR definitionsby obrusvit · c7dc4897 · Aug 29, 2026 · 13 filesMessage 47 · ThinLow 28Details
Commit message · obrusvit
refactor(core): RIIR definitions
[no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 28/100
This commit rewrites the handling of externally downloaded coin/network definitions from Python into Rust. It moves parsing, signature verification, and protobuf decoding into a new Rust module. The change is described by the vendor as a non-security refactor ('RIIR' = 'Rewrite It In Rust') with no changelog entry. The diff itself does not introduce obvious new vulnerabilities, but it is a partial refactor: the Python side now delegates most validation to Rust, and some safety comments rely on assumptions about MicroPython not mutating buffers. There is no vendor statement that this is a security fix or that it addresses a reported vulnerability.
AI review queuedchore(l10n): change Eckhart send__cancel_sign to a questionby Michal Kazda · cb528ee0 · Aug 28, 2026 · 8 filesMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda
chore(l10n): change Eckhart send__cancel_sign to a question [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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only changes the wording of one on-screen message in the Trezor firmware. For the 'Eckhart' design theme, the text 'Cancel sign.' is changed to 'Cancel sign?' (and equivalent changes in Czech, German, Spanish, French, and Portuguese). It is a cosmetic localization tweak with no security effect.
AI review queuedchore(l10n): only add period to send__cancel_sign in Eckhartby Michal Kazda · d07557cd · Aug 27, 2026 · 9 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda
chore(l10n): only add period to send__cancel_sign in Eckhart - remove from Bolt and Caesar, which do not use send__cancel_sign [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 commit is a minor localization cleanup. It removes a trailing period from the 'Cancel sign' translation string in older product layouts (Bolt, Caesar, Delizia) and keeps the period only in the newest layout (Eckhart). It also updates the translation signature file. There is no security relevance.
AI review queuedfix(l10n): update generated filesby Michal Kazda · 40add235 · Aug 27, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda
fix(l10n): update 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 is a routine localization update. It adds one new translated button label ('Cancel sign'), fixes a punctuation mark in another label, and refreshes the generated translation files and their cryptographic signatures. There is no indication of any security issue.
AI review queuedfix(l10n): update generated filesby Michal Kazda · fb9dccd4 · Aug 27, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda
fix(l10n): update 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 is a routine localization update. It adds one new user-facing button label, 'Review', to the Trezor hardware wallet's translation system and regenerates the files that store translated strings and their cryptographic signature. There is no change to security logic, no bug fix, and no vulnerability.
AI review queuedchore(core): remove last uses of `Optional`by M1nd3r · 169e1711 · Aug 26, 2026 · 4 filesMessage 57 · ThinInformational 15Details
Commit message · M1nd3r
chore(core): remove last uses of `Optional`
[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 is a routine code cleanup that replaces the older Optional[Type] style with the newer Type | None style in a few Python files. It also updates the project's automated style checker to enforce the newer style. There is no functional change to the code and no security impact.
AI review queuedchore(core): enforce PEP 585 style [UP006]by M1nd3r · 33b2c0e0 · Aug 26, 2026 · 11 filesMessage 72 · AdequateInformational 15Details
Commit message · M1nd3r
chore(core): enforce PEP 585 style [UP006]
- Removes non-pep585 annotations, e.g. `typing.Tuple` -> `tuple`.
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine code cleanup that updates Python type annotations to a newer, recommended style. It does not change what the code actually does, only how type hints are written. There is no security issue here.
AI review queuedtest(solana): unit test tx header parserby Jakub Janků · fe3e91b5 · Aug 26, 2026 · 1 fileMessage 90 · StrongInformational 15Details
Commit message · Jakub Janků
test(solana): unit test tx header parser
For now, only the header parsing is tested, but the added serialization code can be used in the future to unit test other parts of the Solana TX parser as well.
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds a new unit test file for the Solana transaction parser in the Trezor firmware. It does not change any production code, fix bugs, or alter behavior. It is purely a test/quality improvement with no security relevance.
AI review queuedfix(solana): properly sanitize account countsby Jakub Janků · 5c7fde0c · Aug 26, 2026 · 1 fileMessage 88 · StrongLow 40Details
Commit message · Jakub Janků
fix(solana): properly sanitize account counts
The parsed address counts were previously checked only using asserts which are stripped out in release builds. As a result, the device could misclassify the accounts in a TX and present a writable signer as read-only. However, no funds were at risk, since a TX with invalid counts is rejected by the network.
Moreover, one asserted bound was incorrect, at least one writable signer must be present in each TX (the fee payer).
This commit replaces the asserts with proper if-raise checks that now mirror the on-chain checks, see:
✓ 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
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Low 40/100
This commit fixes a bug in how Trezor's Solana app counted account roles inside a transaction. In release builds, safety checks were removed, so a malformed transaction could trick the device into showing a signer account as read-only on screen. The device would not actually sign anything harmful, because the Solana network would reject the bad transaction anyway. The fix replaces the removed checks with proper error handling and corrects one rule: every transaction must have at least one writable signer to pay fees.
AI review queuedfix(tests): update .dat filesby PrisionMike · 5054fd71 · Aug 26, 2026 · 26 filesMessage 82 · StrongInformational 15Details
Commit message · PrisionMike
fix(tests): update .dat files
- updated timestamps on .dat files avoid CI failures when definition version is bumped during release.
[no changelog]
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
second-pass: unusually broad change
AI analysis · Informational 15/100
This commit only updates test data files (binary .dat fixtures and a UI test fixtures JSON file) to refresh timestamps. The change is explicitly described as avoiding CI test failures when a version number is bumped during release. There is no firmware code change, no user-facing behavior change, and no security relevance.
AI review queueddocs(core): changelog for 2.12.5by Roman Zeyde · 204ca3fd · Aug 26, 2026 · 21 filesMessage 72 · AdequateModerate 69Details
Commit message · Roman Zeyde
docs(core): changelog for 2.12.5
[no changelog]
(cherry picked from commit d2f3aee41be7360b2812fb3d833f6463bfc12dd4)
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Moderate 69/100
This commit is a documentation-only changelog update for the Trezor firmware release 2.12.5. It lists several security fixes that were already made in earlier code changes, including protections for Ethereum swaps and staking, Solana token display and stake lockup confirmation, and Stellar network and signer details. The commit itself does not change any firmware code, but it confirms that the vendor considers these items security-relevant for the release.