TZ
← All projectsTrezor

Trezor firmware

Firmware monorepo for Trezor One, Model T, and Safe devices.

BitcoinHardware walletsNormal
Repository coverage

3768 commits in the local evidence base

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.

1328security candidates435second-pass queue3191AI analyses
201commits · 30 days
450commits · 60 days
1754commits · 180 days
2832commits · 365 days
Backfill bands
Aug 5 → Feb 61298 seen115 candidatesComplete
Feb 6 → Jun 6775 seen58 candidatesComplete
Jun 6 → Jul 6217 seen13 candidatesComplete
Jul 6 → Aug 5360 seen54 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
841Strong · 80–100
1731Adequate · 60–79
1189Thin · 40–59
7Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
tychovrahe394164355667
Jakub Janků1023067681
Roman Zeyde721230639372
obrusvit333135281364
cepetr301111228259
PrisionMike153101149271
Andrew Kozlik893885267
Petr Susil1159286
Martin Pastyřík291025175
M1nd3r292106248071
Ioan Bizău23076230059
Lukas Bielesch1067592066
Analysis record

Published AI watches

Last scanned 30 minutes ago

Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

ci(core): reuse HW tests Slack webhook

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.

abfe74f9by Michal Kazda+1−51 file
No security note in commit
Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): name the skipped cases

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…

98deb5b0by PrisionMike+25−92 files
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): run the cases without display format

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…

05c1f4efby PrisionMike+63−225 files
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(translations): fix failing tutorial test in FR and small update to PT

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…

29cbc419by Michal Kazda+19−193 files
No security note in commit
Informational 10 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core/rust): reduce coverage map size

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)
9bf2fc3aby M1nd3r+1−11 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(translations): sync Crowdin translations

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…

b2e8b5e6by Thalarion+141−1837 files
No security note in commit
Informational 12 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): edge cases for arrays

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
dcdf3068by PrisionMike+169−01 file
No security note in commit
High 70 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): harden task switching against fault injections

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
2f159c6bby cepetr+16−51 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(tests): removed unused is_dynamic

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…

2ada2691by PrisionMike+6−323 files
No security note in commit
Informational 21 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(clear_signing): update proto defs for features to be supported.

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.
84cb6a4bby PrisionMike+1207−979 files
No security note in commit
Informational 19 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(python): fix protocol_v1 probe for bridge transport

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
46492ba4by M1nd3r+18−124 files
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): show language name in change confirm

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…

5ff5cba0by Michal Kazda+295−67 files
No security note in commit
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(translations): fix failing tests in ES and 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…

9a12ab12by Michal Kazda+15−103 files
No security note in commit
Low 47 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(crypto): hardening against potential side-channel leakage

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
7829d7c7by M1nd3r+27−93 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(ci, clear_signing): add clear signing device tests as a nightly run.

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 …

fea125baby PrisionMike+2986−2117 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): move `keccak_32` to unittests

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…

f3225451by Roman Zeyde+8−122 files
No security note in commit
Informational 15 AI analysisMessage 63 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore: remove SmartCash

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
b6d65c00by Roman Zeyde+5−52916 files
No security note in commit
Informational 15 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(common,core,legacy,crypto): remove Groestlcoin

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
e22d597dby Roman Zeyde+41−446845 files
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove Tezos

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 …

433075c0by obrusvit+9531−1751964 files
No security note in commit
Informational 24 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(legacy): lower maximum auto-lock delay to 149 hours

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
c108f275by Ondřej Vejpustek+16−64 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidatefix(core): fix nrf tlv offset calculatiion wrapby tychovrahe · dcdb96bc · Aug 31, 2026 · 1 fileMessage 57 · ThinModerate 61Details
Commit message · tychovrahe

fix(core): fix nrf tlv offset calculatiion wrap

[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
boot or update path
AI analysis · Moderate 61/100

This commit fixes a bug in the Trezor hardware wallet's firmware update code for the nRF wireless chip. The code reads update image headers from an untrusted source and calculates where to look for a SHA-256 hash inside the image. Before the fix, the calculation used a signed offset type and did not check whether the claimed image size was larger than the actual buffer. A malicious or malformed update image could make the offset wrap around (become a small number due to integer overflow), bypassing later safety checks and potentially causing the device to read memory outside the intended buffer. The fix rejects images whose claimed size exceeds the buffer and uses an unsigned type for the offset calculation.

Security candidatefeat(core/caesar): use Marquee in Homescreen labelby obrusvit · 659d5ada · Aug 31, 2026 · 2 filesMessage 62 · AdequateInformational 15Details
Commit message · obrusvit

feat(core/caesar): use Marquee in Homescreen label

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit is a user-interface polish change for the Trezor hardware wallet. It replaces a static text label on the device homescreen with a scrolling 'marquee' label so that longer text (such as a wallet name) can be read even if it does not fit in the available space. There is no security-relevant change here.

Security candidatefix(core/caesar): enlarge progress textby obrusvit · 4cf766b2 · Aug 30, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit

fix(core/caesar): enlarge progress text

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit adjusts how a progress screen on the Trezor device lays out its title text. It makes the title area taller when translations wrap to multiple lines, and re-centers the loading spinner so it does not sit too close to a wrapped title. There is no security-relevant change visible in the code.

Security candidatestyle: run make styleby obrusvit · 9a50f41d · Aug 29, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · obrusvit

style: run make style

[no changelog]

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy path
AI analysis · Informational 15/100

This commit is purely a code-style cleanup. It replaces older Python type-hint syntax (t.Dict, t.Tuple, typing.Iterable) with newer built-in equivalents (dict, tuple, collections.abc.Iterable). No behavior, logic, or security properties of the code were changed.

Security candidatefix(core): check group thresholds of super-shamirby obrusvit · be0cd19b · Aug 29, 2026 · 3 filesMessage 80 · StrongLow 44Details
Commit message · obrusvit

fix(core): check group thresholds of super-shamir

- check the individual group thresholds before comitting the backup
flags
- this prevents a malformed param msg to get the device into the state
of "Backup failed"

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 · Low 44/100

This update fixes a validation gap in the Trezor hardware wallet's Advanced Shamir backup setup. Previously, the device could accept malformed backup settings (such as too many groups or invalid member counts) and end up stuck in a 'Backup failed' state. The fix adds earlier checks so bad settings are rejected before the device commits to the backup process.

Security candidatefeat(core): add `miniscript` feature flagby Roman Zeyde · 3277c744 · Aug 28, 2026 · 18 filesMessage 90 · StrongInformational 15Details
Commit message · Roman Zeyde

feat(core): add `miniscript` feature flag

Will be used to incrementally introduce Miniscript-related features
into the codebase, while excluding them from production FW builds:

- add `miniscript` feature to both firmware and unix builds
- add `trezorminiscript` MicroPython module
- add miniscript-enabled emulator device tests on one model (T3T1)

[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
boot or update path
AI analysis · Informational 15/100

This commit adds a new build-time feature flag called 'miniscript' to the Trezor firmware. It does not implement any actual Miniscript functionality yet; it only creates the scaffolding (a new MicroPython module placeholder, build options, and CI test configurations) so future Miniscript work can be developed without affecting production firmware builds. There is no security-relevant code change here.

Security candidatetest(core): reveal passphrase during {Bolt,Delizia,Eckhart} click testsby Roman Zeyde · f0b7ee37 · Aug 28, 2026 · 4 filesMessage 95 · StrongInformational 15Details
Commit message · Roman Zeyde

test(core): reveal passphrase during {Bolt,Delizia,Eckhart} click tests

Following https://github.com/trezor/trezor-firmware/pull/6851.

[no changelog]

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlcryptography-sensitive pathauthentication path
AI analysis · Informational 15/100

This commit only changes automated test code for Trezor hardware wallets. It updates passphrase tests to use the widest keyboard character ('W' instead of 'a') and adds a step to reveal the hidden passphrase during testing. There is no change to the actual wallet firmware or production code, so it does not create a security vulnerability or fix one in shipped software.

Security candidatefix(core): Avoid raising IndexError during cash address decodingby Fabien · e7ea48d8 · Aug 28, 2026 · 3 filesMessage 100 · StrongLow 39Details
Commit message · Fabien

fix(core): Avoid raising IndexError during cash address decoding

It is possible to craft an invalid cash address that would raise an IndexError and return a confusing error message.

Fill the gap and add tests to ensure a proper ValueError is returned.

Fixes #7749.

[no changelog]

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✓ Links an issue, advisory, or supporting reference
Why it was queued
cryptography-sensitive path
AI analysis · Low 39/100

This commit fixes a bug in how Trezor hardware wallets decode Bitcoin Cash-style 'cashaddr' addresses. Previously, a malformed address could cause the device to hit an internal 'IndexError' and show a confusing message. The fix ensures the address is properly validated and returns a clear 'invalid address' error instead. There is no direct evidence in the commit that this could be used to steal funds, but it improves robustness against bad or maliciously crafted addresses.

Security candidatefeat(core,python): support definitions version 2by obrusvit · 3a9af975 · Aug 28, 2026 · 6 filesMessage 77 · AdequateLow 29Details
Commit message · obrusvit

feat(core,python): support definitions version 2

- version 2 will require only one signature

[no changelog]

77/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
Why it was queued
signing boundary
AI analysis · Low 29/100

This commit adds support for a new 'version 2' format for external definitions in Trezor firmware. The key change is that version 2 requires only one cryptographic signature to validate a definition, whereas version 1 required two. This is a deliberate design change, not a bug, but it reduces the number of independent parties that must sign off before a definition is trusted by the device. The commit does not by itself introduce an exploit, but it lowers the bar for an attacker who could compromise a single signing key or signer.

Security candidatefix(core): render a full-turn sector as a full circleby tychovrahe · 05feac72 · Aug 27, 2026 · 1 fileMessage 85 · StrongInformational 19Details
Commit message · tychovrahe

fix(core): render a full-turn sector as a full circle

`fill_sector` normalizes both endpoints into <0..360), which maps a span
of exactly one turn onto a single value. The octant loop reads that as a
zero-width sector and skips all eight octants, and the centre pixel is
skipped as well, so the call draws nothing at all where a full circle is
meant.

Detect the span before normalizing and pin it to the full range. Only a
forward span counts, so the `start > end` wrap-around convention and every
partial sector keep their existing behaviour. Normalization still runs on
both endpoints first, so its bound assert is never bypassed -- an infinite
endpoint traps rather than silently becoming a circle.

Verified that (0,360), (0,720) and (-360,0) now fill all eight octants
plus the centre, while (0,90), (90,180), (0,359.64), (300,60), (36,108)
and the empty (0,0) are unchanged.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

[no changelog]

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
access control
AI analysis · Informational 19/100

This is a UI graphics bug fix in the Trezor hardware wallet firmware. When drawing a circular progress indicator or pie-chart-like shape spanning a full 360 degrees, the code mistakenly treated it as an empty slice and drew nothing. The patch detects a full-circle span before normalizing the angles and forces it to draw all eight segments plus the center pixel. There is no direct security vulnerability here; it is a rendering correctness fix.

Security candidatefeat(common): report maximal supported passphrase lengthby Roman Zeyde · e393e179 · Aug 27, 2026 · 4 filesMessage 77 · AdequateInformational 19Details
Commit message · Roman Zeyde

feat(common): report maximal supported passphrase length

Legacy & older core models support up to 50 bytes.

[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
access control
AI analysis · Informational 19/100

This commit adds a new informational field to the Trezor device's 'Features' message that tells connected software the maximum passphrase length the device supports. It does not change how passphrases are validated or stored, and it does not fix any known security bug. It is a feature addition to improve compatibility between different Trezor models and wallet software.

Security candidatefeat(core): increase maximum passphrase length to 128 bytesby Roman Zeyde · 835efbb6 · Aug 27, 2026 · 8 filesMessage 87 · StrongInformational 15Details
Commit message · Roman Zeyde

feat(core): increase maximum passphrase length to 128 bytes

Legacy & older core models support up to 50 bytes.

Also, use the same test vectors for all core models.

87/100 · StrongMessage clarity
✓ Specific, 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
access controlfuzzing or regression evidencecryptography-sensitive pathauthentication path
AI analysis · Informational 15/100

This commit simply raises the maximum allowed passphrase length on newer Trezor Core devices from 50 bytes to 128 bytes. It is a feature change, not a security fix or vulnerability. Older and legacy models keep the 50-byte limit. The change is accompanied by updated tests and a new device capability field so software can read the current limit.

Security candidatechore(l10n): add buttons__review for TS7 menu item subtextby Michal Kazda · 60fe7e13 · Aug 27, 2026 · 2 filesMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(l10n): add buttons__review for TS7 menu item subtext
[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 15/100

This is a harmless user-interface wording change. It swaps the label shown beneath two backup-related menu items from a generic 'Review' translation key to a dedicated 'Review' button translation key, and adds that button text to the English translation file. There is no security relevance.

Security candidatefix(core): remove unused confirm_amountby Michal Kazda · 2d36ca0b · Aug 27, 2026 · 4 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda

fix(core): remove unused confirm_amount
[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 simply deletes an unused helper function called confirm_amount from four different user-interface layout files. Because the function was not being called anywhere, removing it cannot change device behavior or introduce a security issue. It is a routine code cleanup.

Security candidatefix(crypto): adjust random_permuteby M1nd3r · b11a85f7 · Aug 27, 2026 · 1 fileMessage 47 · ThinLow 38Details
Commit message · M1nd3r

fix(crypto): adjust random_permute

[no changelog]

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Low 38/100

This commit fixes a function that shuffles arrays (like recovery-seed word order or on-screen PIN layouts) in Trezor's cryptographic code. The original code could misbehave or even crash when given very short or very long inputs, and it used a signed integer type that could turn negative in unexpected ways. The patch adds a safety check, skips shuffling when there is nothing to shuffle, and uses the correct unsigned type. The practical security impact is moderate: it removes a source of non-random or buggy shuffling that could leak information or cause crashes, but the commit itself does not claim to fix an active exploit.

Security candidateperf(core): drop nanopb error strings from bootloaderby tychovrahe · 367cdddc · Aug 27, 2026 · 2 filesMessage 85 · StrongInformational 13Details
Commit message · tychovrahe

perf(core): drop nanopb error strings from bootloader

nanopb's error message strings are linked into the bootloader image, but
nothing reads `pb_(i|o)stream_t::errmsg`. Defining PB_NO_ERRMSG removes
them along with the PB_SET_ERROR code paths.

The three `.errmsg = NULL` initializers in codec_v1.c go away with the
struct field. Dropping them rather than #ifdef-guarding them keeps the
code correct either way, since designated initializers zero the rest.

bootloader_ci is untouched: it has its own messages.c and build.rs.

Recovers 976 B of flash. T3T1 bootloader free space (--production):
28 B -> 1004 B.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

[no changelog]

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trustboot or update path
AI analysis · Informational 13/100

This change removes unused error-message text from the bootloader's copy of the nanopb library to free up about 1 kB of flash storage. The bootloader never looked at these error strings anyway, so the change is a size optimization with no security effect.

Security candidatetest(core): test mock RNGs for Optiga and Tropicby Andrew Kozlik · 972aa929 · Aug 27, 2026 · 5 filesMessage 95 · StrongInformational 12Details
Commit message · Andrew Kozlik

test(core): test mock RNGs for Optiga and Tropic

Adds tests that verify, end to end through the upymod binding and
rng_fill_buffer_strong(), that every entropy source of the model
contributed at every byte position. A dropped source, a lost strong=True,
a truncated buffer fail the tests.

[no changelog]

Co-Authored-By: cepetr <petr@cerninovi.cz>

95/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✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomnesscryptography-sensitive pathseed or entropy path
AI analysis · Informational 12/100

This commit only adds new automated tests and a helper script for generating test data. It does not change the firmware's random number generator, wallet operations, or any user-facing behavior. The goal is to catch future bugs where a hardware model's entropy source might accidentally be left out of the strong randomness mix.

Security candidatefeat(core): add mock RNGs for MCU, Optiga and Tropicby Andrew Kozlik · 14bba1ba · Aug 27, 2026 · 16 filesMessage 77 · AdequateInformational 21Details
Commit message · Andrew Kozlik

feat(core): add mock RNGs for MCU, Optiga and Tropic

[no changelog]

Co-Authored-By: cepetr <petr@cerninovi.cz>

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
entropy or randomnesscryptography-sensitive pathseed or entropy path
AI analysis · Informational 21/100

This commit adds deterministic (predictable) fake random-number generators for Trezor's software emulator only, so automated tests can reproduce exact outputs. It removes the old insecure-prng feature flag from production build paths and gates the new mocks behind emulator-only compile checks. The change is designed to keep fake randomness out of real hardware wallets, but it still increases the amount of insecure-prng code in the repository.

Security candidatefeat(core): increase `ShortString` size to 128 bytesby Roman Zeyde · 9695e1c2 · Aug 27, 2026 · 2 filesMessage 77 · AdequateInformational 17Details
Commit message · Roman Zeyde

feat(core): increase `ShortString` size to 128 bytes

It will allow supporting longer passphrases on Core models.

PIN length is still limited to 50 bytes.

[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
access control
AI analysis · Informational 17/100

This commit simply increases the maximum size of a commonly used short text buffer in the Trezor firmware from 50 bytes to 128 bytes. The stated purpose is to support longer passphrases on Trezor Core devices, while keeping the PIN length limit at 50 bytes. There is no indication in the commit that this fixes a security vulnerability or introduces a security-relevant bug.

Security candidatechore(common, tests, tools): enforce PEP 585 styleby M1nd3r · db40ceb2 · Aug 26, 2026 · 37 filesMessage 72 · AdequateInformational 15Details
Commit message · M1nd3r

chore(common, tests, tools): enforce PEP 585 style

[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
cryptography-sensitive pathsigning or wallet pathboot or update pathauthentication path
AI analysis · Informational 15/100

This commit is a routine code cleanup that updates Python type annotations to follow a newer Python style guide (PEP 585). It replaces older-style imports like `List`, `Tuple`, and `Dict` from the `typing` module with built-in equivalents like `list`, `tuple`, and `dict`. It also adjusts the project's linting configuration to enforce this style. There is no change to runtime behavior, no security fix, and no vulnerability introduced.

Security candidatechore(python): enforce PEP 585 styleby M1nd3r · 5184275b · Aug 26, 2026 · 45 filesMessage 57 · ThinInformational 15Details
Commit message · M1nd3r

chore(python): enforce PEP 585 style

[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 pathauthentication path
AI analysis · Informational 15/100

This commit is a routine code cleanup that updates Python type annotations to a newer, recommended style (PEP 585). It does not change any program logic, security behavior, or runtime functionality. There is no security issue here.

Security candidatechore(core): enforce PEP 585 style [UP035]by M1nd3r · 21e6e3f2 · Aug 26, 2026 · 109 filesMessage 72 · AdequateInformational 15Details
Commit message · M1nd3r

chore(core): enforce PEP 585 style [UP035]

- Replaces deprecated imports, e.g. `typing.Sequence` -> `collections.abc.Sequence`.

[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 pathseed or entropy pathsigning or wallet pathauthentication pathparser or protocol path
AI analysis · Informational 15/100

This is a large but purely cosmetic code cleanup in the Trezor firmware repository. It replaces old-style Python type-hint imports (such as typing.Sequence) with their modern equivalents (collections.abc.Sequence) to follow the PEP 585 style guide. No program logic, security checks, cryptography, or user-facing behavior was changed. The commit explicitly says '[no changelog]' and labels itself as a 'chore'.

Security candidatefix(core): use with_colon instead of += ":" in for descriptionsby Michal Kazda · 77cde7c6 · Aug 26, 2026 · 2 filesMessage 77 · AdequateInformational 16Details
Commit message · Michal Kazda

fix(core): use with_colon instead of += ":" in for descriptions
- affects only Bolt and Caesar
[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 16/100

This commit is a small UI cleanup in Trezor's firmware. It replaces several places where a colon was manually added to on-screen text descriptions with a helper function called with_colon(). The change only affects two visual themes (Bolt and Caesar). It is not a security fix and does not change how funds, keys, or transactions are protected.

Security candidatechore(translations): updated translation signaturesby Michal Kazda · 15d3f914 · Aug 26, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): updated translation signatures
[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 boundarysigning or wallet pathtranslation-only discount
AI analysis · Informational 15/100

This commit simply refreshes the digital signature metadata for translation files in a JSON configuration. There is no code change, no new feature, and no apparent security fix. It appears to be routine maintenance.

Security candidatechore(translations): added missing PTBR glyph Éby Michal Kazda · e514f155 · Aug 26, 2026 · 24 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda

chore(translations): added missing PTBR glyph É
[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 adds a single missing Portuguese-Brazilian character (É) to font files used by the Trezor hardware wallet. It is a routine translation/localization fix with no security relevance.