Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…
This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…
No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…
test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…
Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…
This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…
Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…
No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…
This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…
This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…
Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …
This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…
This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…
No security-relevant signals detectedPure feature removal / code cleanup
This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…
No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …
This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…
Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathboot or update pathauthentication path
AI analysis · Low 27/100
This commit fixes how long text is shown on Trezor Safe 3 and similar devices using the 'Bolt' user interface. Previously, long messages in confirmation dialogs could be cut off or not fully visible. Now these dialogs can paginate (split across multiple swipeable pages) so users can read the entire content before approving. The change is a UI/UX improvement rather than a direct exploit fix, but truncated security warnings could theoretically lead users to confirm something they did not fully see.
Security candidatefix(core/bolt): Marquee for PIN promptby obrusvit · 5b2b65d5 · Oct 27, 2026 · 2 filesMessage 57 · ThinInformational 20Details
Commit message · obrusvit
fix(core/bolt): Marquee for PIN prompt
[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
access controlauthentication path
AI analysis · Informational 20/100
This commit changes the PIN entry screen so that long prompt text scrolls smoothly like a marquee instead of being crammed or clipped. It is a user-interface polish fix with no apparent security relevance.
Lower-priorityfix(core/bolt): two-line title ShareWordsby obrusvit · 3eecb070 · Oct 27, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · obrusvit
fix(core/bolt): two-line title ShareWords
- longer title would shift the words downwards
[no changelog]
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritychore(vendor): add STM32H5 HAL and CMSIS deviceby bleska · 8a3561d9 · Oct 27, 2026 · 5 filesMessage 72 · AdequateTriage 0Details
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
AI review queuedfix(translations): fix failing tests in PTBR and ESby Michal Kazda · efbedc41 · Oct 27, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda
fix(translations): fix failing tests in PTBR and ES [no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit updates Spanish and Portuguese translation files for the Trezor hardware wallet. It shortens a few on-screen phrases and splits one phrase into separate versions for different device models so that text fits on screen correctly. There is no security change here—this is purely a translation and layout fix for failing tests.
Security candidatefix(core): give USB EP0 receptions a full-packet bufferby tychovrahe · 0b9ac86f · Oct 27, 2026 · 7 filesMessage 85 · StrongHigh 77Details
Commit message · tychovrahe
fix(core): give USB EP0 receptions a full-packet buffer
- the OTG core accepts a full packet on EP0 OUT however short the armed length; the stack armed the status stage with a NULL buffer and VCP received class requests into an 8-byte one, so a host could make the HAL write through NULL or past the VCP buffer - receive all of them into a packet-sized buffer in the device handle
Co-Authored-By: Claude Opus 5.5 <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
boot or update path
AI analysis · High 77/100
This commit fixes a USB memory-safety bug in Trezor hardware wallets. When the device expected no data during the final 'status' handshake of a USB control transfer, it told the USB hardware to write incoming bytes to address zero (NULL) or into an 8-byte command buffer. The USB hardware can actually deliver a full 64-byte packet regardless of what length was requested, so a malicious or misbehaving USB host could make the device write memory past the intended location or through the NULL pointer, causing a crash or potentially worse. The fix gives every such reception a dedicated 64-byte buffer inside the device handle.
fix(core): handle missing USB device qualifier descriptor
- answer device qualifier requests with a control error when the class provides no descriptor instead of calling a NULL pointer - apply the same check to the other speed configuration descriptor
[no changelog]
Co-Authored-By: Claude Opus 5.5 <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
Lower-priorityfix(core): reject malformed BLE unpair addressby tychovrahe · fcc4e719 · Oct 27, 2026 · 4 filesMessage 80 · StrongTriage 8Details
Commit message · tychovrahe
fix(core): reject malformed BLE unpair address
- validate the address length in BleUnpair before the prompt - raise ValueError instead of a fatal error in trezorble.unpair
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
defensive validation
Lower-priorityci(core): set pytest session timeout for click testsby Roman Zeyde · 5ee41936 · Oct 27, 2026 · 1 fileMessage 99 · StrongTriage 0Details
Commit message · Roman Zeyde
ci(core): set pytest session timeout for click tests
Otherwise, CI jobs are cancelled - without showing the test results.
[no changelog]
99/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode✓ Mentions testing or verification
feat(tests,clear_signing): update definition fixtures from dev
[no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 15/100
This commit updates an internal helper script used to refresh test data for Ethereum 'clear signing' definitions. It adds an optional --dev mode so developers can fetch unsigned development definitions from an internal-only server and verify them with development keys. There is no change to the firmware that runs on customer devices, no change to production signature verification, and no disclosed security issue.
Lower-priorityfeat(core): list prodtest completions on 2nd tabby Andrew Kozlik · 91b01f30 · Oct 26, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Andrew Kozlik
feat(core): list prodtest completions on 2nd tab
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidaterefactor(core): rename feature noise to noise_kk1by Martin Milata · 32d898c2 · Oct 26, 2026 · 3 filesMessage 57 · ThinInformational 15Details
Commit message · Martin Milata
refactor(core): rename feature noise to noise_kk1
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This commit is a simple internal rename of a Rust build feature from 'noise' to 'noise_kk1' and removes one unused source file ('noise_xxpsk3.c') from the build. There is no change to how the device works, no bug fix, and no security-relevant behavior change visible in the diff.
Lower-priorityfix(core): sort prodtest help output by nameby Andrew Kozlik · fbcda1fd · Oct 26, 2026 · 3 filesMessage 57 · ThinTriage 0Details
Commit message · Andrew Kozlik
fix(core): sort prodtest help output by name
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritydocs: update Tron entry at `coins-bip44-paths.md`by Roman Zeyde · 7c82b2c4 · Oct 26, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Roman Zeyde
docs: update Tron entry at `coins-bip44-paths.md`
[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
documentation-only discount
Lower-prioritydocs: drop Ontology from `coins-bip44-paths.md`by Roman Zeyde · cda46a77 · Oct 26, 2026 · 1 fileMessage 88 · StrongTriage 0Details
Commit message · Roman Zeyde
docs: drop Ontology from `coins-bip44-paths.md`
It was removed in https://github.com/trezor/trezor-firmware/pull/1776/changes/e974c809da18f863d9a9a6f6840b52fb0c6ca07e.
[no changelog]
88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
documentation-only discount
Security candidatefix(core/bootloader): initialize BLE once on the wipe path [no changelog]by tychovrahe · e59fe6ac · Oct 26, 2026 · 2 filesMessage 85 · StrongInformational 18Details
Commit message · tychovrahe
fix(core/bootloader): initialize BLE once on the wipe path [no changelog]
drivers_init() already brought the driver up; the wipe branch called ble_init() a second time. The STM32 driver ignores a repeated init, the unix one re-registered its handles and failed, so a wipe boot command ended on the failure screen in the emulator. Drop the second call and give the unix driver the same already-initialized guard.
Co-Authored-By: Claude Fable 5.1 <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
update trustboot or update path
AI analysis · Informational 18/100
This is a small bug fix in the Trezor bootloader's wipe feature. When wiping the device, the code was accidentally initializing the Bluetooth (BLE) system twice. On real hardware the second call was ignored, but in the software emulator it caused the wipe process to end on an error screen. The patch removes the redundant second initialization and also makes the emulator's BLE driver ignore repeated initializations, matching the real hardware behavior. It does not appear to be a security vulnerability.
AI review queuedfix(solana): verify accounts in sysvar slotsby Jakub Janků · f1e3d96e · Oct 26, 2026 · 8 filesMessage 90 · StrongHigh 76Details
Commit message · Jakub Janků
fix(solana): verify accounts in sysvar slots
- The Stake program v5 made the sysvar accounts optional and picks the account layout by checking whether the sysvar slot holds the sysvar, so another account there shifts the following accounts into roles different from the ones shown on the device. - Solana is moving away from sysvar account references in program ABIs in general, so reject anything but the named sysvar in these slots to catch similar changes in other programs as well. - Fix the claim fixtures that passed the ComputeBudget program as the stake history sysvar.
Co-Authored-By: Claude Mythos 5.1 <noreply@anthropic.com> (cherry picked from commit 9b4b571e3c4c406a7cb5dda0e097647f91f218e4)
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 · High 76/100
This update fixes a security issue in how Trezor handles Solana transactions. Some Solana programs use special 'sysvar' accounts in fixed slots. A malicious transaction could put a different account into one of those slots, causing the device to interpret the remaining accounts incorrectly and approve a transaction that looks safe on screen but does something else on the blockchain. The fix makes the device reject any transaction where a sysvar slot does not contain the exact expected sysvar account.
Lower-priorityrefactor(core): gate task scheduling to save flash spaceby cepetr · 50d4e2ab · Oct 26, 2026 · 6 filesMessage 62 · AdequateTriage 0Details
Commit message · cepetr
refactor(core): gate task scheduling to save flash space
[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
AI review queuedchore: remove 'confidential_assets' entry from coin definitionsby Roman Zeyde · bca652d5 · Oct 26, 2026 · 61 filesMessage 93 · StrongInformational 15Details
Commit message · Roman Zeyde
chore: remove 'confidential_assets' entry from coin definitions
It was never used, since https://github.com/trezor/trezor-firmware/commit/b854b64706b7e7019d29b0ae6db1b0f0aa82426f was not merged.
[no changelog]
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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply removes an unused configuration field called 'confidential_assets' from cryptocurrency definition files and from the code that reads them. The field was never active in the firmware, so this is a cleanup change with no security impact.
Security candidatefeat(core,legacy): restrict xpub exportby Petr Susil · f5184bdd · Oct 26, 2026 · 27 filesMessage 80 · StrongLow 46Details
Commit message · Petr Susil
feat(core,legacy): restrict xpub export
Quantum computers may break exported xpubs. Warn before exporting xpubs shallower than 2 levels (except known third-party paths) and of SLIP-15, SLIP-16 and BIP-85.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> (cherry picked from commit 0b594247cd3342949b4888bb1f4e89dc641f8384)
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
cryptography-sensitive pathsigning or wallet pathboot or update path
AI analysis · Low 46/100
This commit adds a warning to Trezor devices when a user tries to export an extended public key (xpub) from a path that is considered risky in a future quantum-computing scenario. It does not block the export, but it makes the user confirm they understand the risk. The affected paths are very shallow ones (less than two derivation levels) and paths used for encryption keys or derived passwords (SLIP-15, SLIP-16, BIP-85). Some well-known third-party uses of shallow paths are allowed without a warning. This is a hardening change, not a fix for an active bug or exploit.
fix(cardano): implement cip-129 for drep credentials
Fixes Cardano staking: Custom DRep address may not match the address shown on the device Fixes #6192
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
credential or privilege state
AI analysis · Moderate 59/100
This update fixes how Trezor displays Cardano DRep (delegated representative) addresses on the device screen. Previously, the device used an older bech32 format that could show a different address than what the user expected, potentially leading them to delegate voting power to the wrong representative. The fix adopts the newer CIP-129 standard so the displayed address matches the one used on the blockchain.
Security candidatefix(core/caesar): hold to confirm firmware updateby obrusvit · a95d9b94 · Oct 25, 2026 · 1 fileMessage 80 · StrongLow 28Details
Commit message · obrusvit
fix(core/caesar): hold to confirm firmware update
- The screen before rebooting to the bootloader was confirmed by a single right press since the new menu navigation, base used both buttons. - Pressing both buttons would clash with "Shift", so it is a hold.
[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
update trustcryptography-sensitive pathboot or update path
AI analysis · Low 28/100
This commit changes how a user confirms a firmware update on the Trezor Safe 3 (Caesar layout). Previously, pressing the right button once could confirm the update; now the user must hold a button for a short period. The change prevents accidental or malicious confirmations when the right-button press is part of a different navigation gesture, and it avoids conflict with the new 'Shift' action that uses both buttons.
- When types in (contract,token) we request host for a clear name for the contract. [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 boundarysigning or wallet path
AI analysis · Low 26/100
This commit adds a new optional feature to Trezor's Ethereum clear-signing system. When a transaction field is marked as an address name and its type is 'contract' or 'token', the device can now ask the connected computer (host) to look up a friendly name for that address. If the host provides a name, the device shows that name to the user instead of the raw address. The change is a feature addition, not a direct fix for a known security bug, but it touches the code that decides what text users see on their device screen during transaction approval.
AI review queuedfeat(ethereum): request host for known address names.by PrisionMike · dc17456e · Oct 24, 2026 · 5 filesMessage 62 · AdequateLow 27Details
Commit message · PrisionMike
feat(ethereum): request host for known address names.
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 27/100
This commit adds a feature that lets the Trezor device ask the connected computer (the 'host') for human-readable names of Ethereum addresses it doesn't already know. The device then shows those names on its screen during transaction signing. The change also moves some helper code between files and makes address-name lookups happen in more places, such as when displaying nested contract calls and token approvals. There is no direct evidence in the commit that this fixes a security bug; it reads as a user-experience feature for clearer transaction confirmation.
Lower-prioritychore: code comment to flag vault addresses as irremovableby PrisionMike · 8bf74721 · Oct 24, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · PrisionMike
chore: code comment to flag vault addresses as irremovable
[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