Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…
This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…
No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…
test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…
Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…
This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…
Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…
No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…
This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…
This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…
Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …
This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…
This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…
No security-relevant signals detectedPure feature removal / code cleanup
This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…
No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …
This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…
Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Security candidatechore(python): fixup `noqa:` comment following Ruff nitby Roman Zeyde · 72489948 · Oct 19, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · Roman Zeyde
chore(python): fixup `noqa:` comment following Ruff nit
``` warning: Invalid `# noqa` directive on src/trezorlib/qt/pinmatrix.py:36: expected a comma-separated list of codes (e.g., `# noqa: F401, F841`). warning: Invalid `# noqa` directive on src/trezorlib/qt/pinmatrix.py:37: expected a comma-separated list of codes (e.g., `# noqa: F401, F841`). ```
[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
authentication path
AI analysis · Informational 15/100
This is a trivial Python linting cleanup. It changes two `# noqa: I` comments to `# noqa: I900` so that the Ruff linter accepts them. No code behavior is altered, and there is no security relevance.
It will be used to format BIP-380 key expressions (for descriptor formatting).
[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
Lower-priorityfix(python): make `TropicModel.stop()` idempotentby Ondřej Vejpustek · 98d88933 · Oct 19, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
fix(python): make `TropicModel.stop()` idempotent
A second `stop()` call survived the no-op `send_signal()` but crashed on `_RUNNING_PIDS.remove()` with a `KeyError`. Clear `self.process`, like `Emulator.stop()` does.
[no changelog]
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-prioritydocs: update the Tropic model ports in `AGENTS.md`by Ondřej Vejpustek · 80f3186d · Oct 19, 2026 · 1 fileMessage 95 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
docs: update the Tropic model ports in `AGENTS.md`
The auto-started model no longer runs on a fixed TCP 28992 and the `port + 6` slot is gone from the emulator port block. 28992 remains the place where a manually started `model_server`, the T3W1 unit tests and the pre-2.9.4 upgrade-test emulators look.
[no changelog]
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
documentation-only discount
Lower-priorityfeat(core): start the TROPIC01 model only for Tropic modelsby Ondřej Vejpustek · 0f5ce130 · Oct 19, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(core): start the TROPIC01 model only for Tropic models
`prodtest_emu.py` now autodetects Tropic support from the emulator properties, like `emu.py` does. `--tropic-emulator` defaults to the `tropic` property of the binary and the model is only started when it is set. `TROPIC_MODEL_PORT` is not announced when the binary has no Tropic.
[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
Lower-priorityrefactor(python): move `Emulator.properties()` to the base classby Ondřej Vejpustek · 3a195820 · Oct 19, 2026 · 1 fileMessage 97 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
refactor(python): move `Emulator.properties()` to the base class
`LegacyEmulator` keeps the empty stub because the legacy emulator ignores command-line arguments and `--emulator-properties` would just start it.
[no changelog]
97/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
Lower-priorityfeat(core): support `--emulator-properties` in the prodtest emulatorby Ondřej Vejpustek · f0056889 · Oct 19, 2026 · 1 fileMessage 97 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(core): support `--emulator-properties` in the prodtest emulator
Print the same JSON as the firmware emulator and exit, so that `Emulator.properties()` can detect what the binary was built with.
[no changelog]
97/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
Security candidatefix(core/caesar): show SHIFT label by defaultby obrusvit · 53400258 · Oct 19, 2026 · 2 filesMessage 80 · StrongInformational 15Details
Commit message · obrusvit
fix(core/caesar): show SHIFT label by default
- show the SHIFT label by default in all screens when the shift functionality is activated - previously, this was only in the tutorial
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 path
AI analysis · Informational 15/100
This commit is a small user-interface cleanup for the Trezor hardware wallet's 'Caesar' layout. It makes the on-screen 'SHIFT' label appear by default whenever the Shift button feature is active, instead of only showing it in the tutorial. The change removes a special override that the tutorial used and applies the same label everywhere. There is no security issue here.
Security candidatefeat(core/caesar): new tutorialby obrusvit · 6c6bd120 · Oct 19, 2026 · 9 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit
feat(core/caesar): new tutorial
- new tutorial implementation teaching the new menu and SHIFT-to-scroll up navigation
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 pathboot or update path
AI analysis · Informational 15/100
This commit is a routine user-interface feature: it adds a new on-device tutorial for the Trezor hardware wallet's 'Caesar' layout. It teaches users how to navigate menus, scroll, use the middle button, and the 'Shift' button combination. There is no security fix or vulnerability present in the change.
Lower-prioritychore(vendor): use mldsa-native v2.0.0by M1nd3r · 2199df1a · Oct 19, 2026 · 1 fileMessage 88 · StrongTriage 0Details
Commit message · M1nd3r
chore(vendor): use mldsa-native v2.0.0
- Previously used release was a beta (v1.0.0-beta): https://github.com/pq-code-package/mldsa-native/releases#release-v1.0.0-beta
✓ 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
Lower-priorityfix: replace deprecated calls in `shell.nix`by M1nd3r · 3cd652a3 · Oct 19, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · M1nd3r
fix: replace deprecated calls in `shell.nix`
- `stdenv.isDarwin` is deprecated, using `stdenv.hostPlatform.isDarwin` instead. - `stdenv.isAarch64` is deprecated, using `stdenv.hostPlatform.isAarch64` instead.
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI review queuedfix(core/emulator): fix crash in micropython built with --asanby cepetr · 44c5a701 · Oct 19, 2026 · 4 filesMessage 62 · AdequateInformational 16Details
Commit message · cepetr
fix(core/emulator): fix crash in micropython built with --asan
[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
second-pass: broader security terminology
AI analysis · Informational 16/100
This commit fixes a crash that happened only when running the Trezor firmware emulator with AddressSanitizer (ASAN), a debugging tool used during development. The crash occurred because ASAN's stack-use-after-return detection interfered with MicroPython's internal stack check, causing a false RuntimeError on startup. The fix disables that specific ASAN feature for emulator builds and also turns off leak detection because the firmware does not use the heap. This change only affects developer/debug builds and does not change the security behavior of real Trezor devices.
Lower-priorityfix(core/xbuild): do not configure linker under rust-analyzerby cepetr · 2b5e4c9a · Oct 18, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · cepetr
fix(core/xbuild): do not configure linker under rust-analyzer
[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
Lower-priorityfeat(core/xtask): exclude secmon from rust-analyzer configby cepetr · cb8197d1 · Oct 18, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · cepetr
feat(core/xtask): exclude secmon from rust-analyzer config
[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
Security candidatefeat(core/caesar): show scrollbar in menuby obrusvit · 90294f2a · Oct 17, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
feat(core/caesar): show scrollbar in menu
- both FW and BLD menu
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 user-interface polish change for the Trezor hardware wallet's 'Caesar' layout. It adds a small page counter (like '1/3') and a scrollbar-style indicator to on-device menus in both the bootloader and firmware. There is no security-relevant change; it only affects what is drawn on screen.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
update trustcryptography-sensitive pathboot or update path
AI analysis · Informational 12/100
This commit reorganizes the on-screen button and menu code used by the Trezor bootloader on small-screen devices (T2B1/T3B1). It creates bootloader-specific copies of user-interface components instead of sharing them with the main firmware, and removes unused button layout helpers. The stated goal is to reduce flash memory use and make the bootloader UI independent from firmware UI changes. There is no indication in the commit that this fixes a security bug or changes security-critical behavior.
fix(core/embed): validate optiga metadata item length before storing it
On truncated input, `optiga_parse_metadata()` returned an error, but only after storing a pointer/length pair reaching past the end of the input buffer into the output struct. This was harmless for callers that check the return value, but it broke the guarantee that the zero-initialized output never holds an out-of-bounds range. Check the value length before storing the item.
[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
defensive validation
AI review queuedfix(core/embed): accept zero-length TLV item at the end of optiga metadataby Ondřej Vejpustek · d8ae06db · Oct 16, 2026 · 1 fileMessage 85 · StrongLow 42Details
Commit message · Ondřej Vejpustek
fix(core/embed): accept zero-length TLV item at the end of optiga metadata
`optiga_parse_metadata()` rejected a zero-length item in final position while accepting it anywhere else. Relax the bounds check accordingly.
[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
second-pass: broader security terminology
AI analysis · Low 42/100
This is a small bug fix in the Trezor hardware wallet firmware. It changes a bounds check so that a zero-length data item at the very end of a metadata block is accepted, just like zero-length items already are elsewhere in the block. Without the fix, a valid but empty trailing item would be rejected as malformed. This could cause communication problems with the Optiga security chip, but the change itself is a straightforward correction of an overly strict check.
fix(core/embed): fix off-by-one in optiga metadata length check
The length of the serialized metadata TLV-Object is stored in a single byte, so the maximum representable payload length is 255 bytes. `optiga_serialize_metadata()` only rejected payloads larger than 256 bytes, so a payload of exactly 256 bytes was truncated to a length byte of 0 while still returning `OPTIGA_SUCCESS`. Unreachable with current callers, whose buffers are capped at `OPTIGA_MAX_METADATA_SIZE` (44) bytes.
[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
get_glyph() narrowed chars with `as u16`, so a code point above U+FFFF was drawn with the glyph of the BMP char sharing its low 16 bits (e.g. U+10041 as 'A'). Two different strings could thus render identically while signing different bytes. Draw such chars with the nonprintable glyph instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit f0d78f8fe65b1eac885a048b3173af1deb3a86b8)
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
signing boundary
AI analysis · High 74/100
This commit fixes a display bug in Trezor hardware wallets where special Unicode characters above U+FFFF (so-called supplementary plane characters) were incorrectly drawn as completely different, ordinary characters. For example, a rare character U+10041 could appear on screen as the letter 'A'. Because the device signs the original bytes but the user sees a misleading string, an attacker could craft a transaction or message that looks legitimate to the user while actually signing something different. The fix now shows a non-printable placeholder for such characters instead of the wrong glyph.
Security candidatefeat(core/caesar): new menu nav in bootloaderby obrusvit · 07d2c3d6 · Oct 16, 2026 · 14 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
feat(core/caesar): new menu nav in bootloader
[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
update trustcryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a routine user-interface redesign for the bootloader on certain Trezor hardware wallets. It changes how buttons are labeled and how users navigate confirmation menus (for example, moving the fingerprint info screen into a context menu and requiring both buttons for factory reset). There is no indication of a security bug being fixed or introduced.
AI review queuedchore(python): remove deprecated `details` argument from `btc.sign_tx()`by Roman Zeyde · 95accc10 · Oct 16, 2026 · 2 filesMessage 77 · AdequateInformational 20Details
Commit message · Roman Zeyde
chore(python): remove deprecated `details` argument from `btc.sign_tx()`
It was deprecated in 3d6d1a56ac595866b0d826445caeb429bac13a26.
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 20/100
This is a routine cleanup in Trezor's Python library. It removes an old, already-deprecated way of passing extra transaction signing options (the `details` argument) from the `btc.sign_tx()` helper. Users who still relied on that old argument will now get a normal Python error instead of a deprecation warning, but the change does not fix or introduce any security vulnerability.
Security candidatebuild(core): suppress LOAD segment with RWX permissions warningby Martin Milata · b769435c · Oct 15, 2026 · 1 fileMessage 62 · AdequateInformational 11Details
Commit message · Martin Milata
build(core): suppress LOAD segment with RWX permissions warning
[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
credential or privilege state
AI analysis · Informational 11/100
This commit changes the build settings for the Trezor firmware's Rust code to silence a linker warning about memory segments that are marked as readable, writable, and executable (RWX). The commit message states that these segment permissions are not actually used to configure the device's Memory Protection Unit (MPU), so the warning is not a real security concern. It does not fix a vulnerability, but it does hide a warning that could otherwise alert developers to a potentially risky memory layout.
Lower-priorityfeat(core): read the emulator storage filenames from the environmentby Ondřej Vejpustek · 864d3f0a · Oct 15, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(core): read the emulator storage filenames from the environment
The unix emulator reads the flash and sdcard filenames from the `TREZOR_FLASH_FILENAME` and `TREZOR_SDCARD_FILENAME` environment variables, falling back to the usual `trezor.flash` and `trezor.sdcard`. An empty value in the environment is an error now.
[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
Lower-priorityfeat(python): pass the storage filenames to the emulatorby Ondřej Vejpustek · 73efc7b8 · Oct 15, 2026 · 2 filesMessage 85 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(python): pass the storage filenames to the emulator
The `Emulator` classes pass `STORAGE_FILENAME` and `SDCARD_FILENAME` to the emulator via the environment, making the Python constants the single source of truth for the names.
[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