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
1762commits · 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 3 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 candidatechore(translations): replace backup__title_backup_wallet with reset__recovery_wallet_backup_titleby Michal Kazda · f7e36aa3 · Nov 2, 2026 · 5 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): replace backup__title_backup_wallet with reset__recovery_wallet_backup_title
- simplifies and unifies the terminology
- makes backup__title_backup_wallet obsolete, so it is removed
[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 pathboot or update path
AI analysis · Informational 15/100

This commit is a routine user-interface cleanup: it swaps one on-screen title ('Back up wallet') for another existing title ('Recovery wallet backup') and removes the old translation key. There is no security change, no bug fix, and no behavior change beyond the visible label text.

Security candidatechore(translations): replace reset__check_backup_title with recovery__title_dry_runby Michal Kazda · 722778d7 · Nov 2, 2026 · 6 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda

chore(translations): replace reset__check_backup_title with recovery__title_dry_run
- simplifies and unifies the terminology
- makes reset__check_backup_title obsolete, so it is removed
[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 pathboot or update path
AI analysis · Informational 15/100

This commit is a routine cleanup of on-screen text labels. It replaces one internal label name (reset__check_backup_title) with another (recovery__title_dry_run) that already exists, and removes the old label from translation files. The actual user-facing text shown on the device does not change: both labels display 'Check backup' on the affected device layouts. There is no security-relevant code change.

Security candidatestyle: remove quotes from type annotationsby M1nd3r · d8ab1ed0 · Oct 30, 2026 · 45 filesMessage 45 · ThinInformational 15Details
Commit message · M1nd3r

style: remove quotes from type annotations

[no changelog]

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update pathauthentication pathparser or protocol path
AI analysis · Informational 15/100

This commit is a pure code-style cleanup. It removes unnecessary quotation marks around type annotations (for example, changing 'Session' to Session) across many Python files. These changes do not alter what the code does, how it handles data, or how it protects secrets. There is no security impact.

Security candidatestyle: use PEP 604 syntax where possibleby M1nd3r · a68d4ee0 · Oct 30, 2026 · 38 filesMessage 68 · AdequateInformational 15Details
Commit message · M1nd3r

style: use PEP 604 syntax where possible

- Replaced `Optional[X]` annotation by PEP 604 syntax `X | None` where possible.
- Replaced `Union[X, Y]` annotation by PEP 604 syntax `X | Y` where possible.
- Added `from __future__ import annotations` where necessary.

[no changelog]

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathboot or update pathauthentication path
AI analysis · Informational 15/100

This is a pure code-style cleanup. It replaces older Python type annotations like `Optional[X]` and `Union[X, Y]` with the newer `X | None` and `X | Y` syntax, and adds `from __future__ import annotations` where needed so the new syntax works on Python 3.9. No behavior of the code changes, and there is no security relevance.

Security candidatechore(core): drop MetaMask EIP-7702 supportby Roman Zeyde · 1528e6ea · Oct 30, 2026 · 7 filesMessage 57 · ThinInformational 18Details
Commit message · Roman Zeyde

chore(core): drop MetaMask EIP-7702 support

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

This commit removes built-in support for MetaMask's EIP-7702 smart-contract wallet delegation address from Trezor firmware. After this change, Trezor will no longer recognize MetaMask's specific delegation contract as a trusted/known delegate, so any EIP-7702 authorization using that MetaMask address will be rejected with an 'Unknown EIP-7702 delegate address' error instead of being signed. This is a deliberate feature removal, not a code vulnerability fix. It reduces the attack surface by no longer blessing a third-party contract as a known delegate, but it does not patch an exploitable bug.

Lower-prioritychore(deps): update filelock and virtualenvby M1nd3r · 5a8b1cfb · Oct 30, 2026 · 2 filesMessage 93 · StrongTriage 0Details
Commit message · M1nd3r

chore(deps): update filelock and virtualenv

- Updated filelock v3.32.5 -> v4.2.4
- Updated virtualenv v21.14.12 -> v21.14.13

Should resolve the following issues:
- https://github.com/trezor/trezor-firmware/security/dependabot/211
- https://github.com/trezor/trezor-firmware/security/dependabot/219
- https://github.com/trezor/trezor-firmware/security/dependabot/220
- https://github.com/trezor/trezor-firmware/security/dependabot/221
- https://github.com/trezor/trezor-firmware/security/dependabot/223
- https://github.com/trezor/trezor-firmware/security/dependabot/224
- https://github.com/trezor/trezor-firmware/security/dependabot/225
- https://github.com/trezor/trezor-firmware/security/dependabot/226
- https://github.com/trezor/trezor-firmware/security/dependabot/227
- https://github.com/trezor/trezor-firmware/security/dependabot/228
- https://github.com/trezor/trezor-firmware/security/dependabot/229
- https://github.com/trezor/trezor-firmware/security/dependabot/230
- https://github.com/trezor/trezor-firmware/security/dependabot/231

93/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
automated dependency-update discount
Lower-priority chore(deps): update astroid and pylintby M1nd3r · 16f84fbc · Oct 30, 2026 · 2 filesMessage 93 · StrongTriage 0Details
Commit message · M1nd3r

chore(deps): update astroid and pylint

- Updated astroid v3.3.11 -> v4.3.4
- Updated pylint v3.3.9 -> v4.1.3

- Resolves https://github.com/trezor/trezor-firmware/security/dependabot/222.
- Might bring performance improvements.

93/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
automated dependency-update discount
Lower-prioritychore(core/secmon): decrease secmon stack and RAM sizesby M1nd3r · 49df7b39 · Oct 30, 2026 · 5 filesMessage 93 · StrongTriage 0Details
Commit message · M1nd3r

chore(core/secmon): decrease secmon stack and RAM sizes

- Decreased RAM size to 64 kB (from 96 kB).
- Decreased STACK size to 32 kB (from 80 kB).

- Followup to https://github.com/trezor/trezor-firmware/pull/8199.

[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
Security candidatechore(crypto): enable `MLD_CONFIG_REDUCE_RAM`by M1nd3r · fcf63e11 · Oct 30, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · M1nd3r

chore(crypto): enable `MLD_CONFIG_REDUCE_RAM`

- This option significantly decreases the stack required for ML-DSA operations, with acceptable slowdown.

[no changelog]

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100

This commit turns on a build-time option called MLD_CONFIG_REDUCE_RAM for the ML-DSA cryptographic code used in Trezor firmware. The stated purpose is to lower the amount of stack memory consumed during ML-DSA (post-quantum digital signature) operations, accepting a small performance slowdown. There is no indication in the commit that this fixes a security bug, vulnerability, or exploit. It appears to be a routine memory-optimization change.

Lower-priorityrefactor(python): handle TREZOR_PATH the same way in CLI and device testsby Martin Milata · d6b3137c · Oct 30, 2026 · 4 filesMessage 72 · AdequateTriage 0Details
Commit message · Martin Milata

refactor(python): handle TREZOR_PATH the same way in CLI and device tests

[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
Security candidatebuild(legacy): remove unused `USE_ASM_ARM` flagby Roman Zeyde · 10d0c5d4 · Oct 30, 2026 · 1 fileMessage 88 · StrongInformational 15Details
Commit message · Roman Zeyde

build(legacy): remove unused `USE_ASM_ARM` flag

It was added in 52d34955e7 to our code, but never used in C code.
It was introduced to upstream by https://github.com/bitcoin-core/secp256k1/pull/366/changes/001f1763c76c2f5599cdb8713692c618191226fe

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

This commit removes an unused compiler flag from the build system for the older Trezor firmware. The flag was defined but never referenced anywhere in the source code, so removing it has no functional or security effect.

Security candidatebuild(core+legacy+crypto): remove unused `ENABLE_MODULE_GENERATOR` flagby Roman Zeyde · e4af4d9f · Oct 30, 2026 · 3 filesMessage 93 · StrongInformational 15Details
Commit message · Roman Zeyde

build(core+legacy+crypto): remove unused `ENABLE_MODULE_GENERATOR` flag

It is part of the https://github.com/BlockstreamResearch/secp256k1-zkp fork (added in 52d34955e7).
After we moved to https://github.com/bitcoin-core/secp256k1 (in 67f3af619a) it's no longer used.

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

This commit removes an unused compiler flag called ENABLE_MODULE_GENERATOR from three build files. The flag was left over from an older version of a cryptographic library and no longer has any effect after Trezor switched to a different library version. There is no functional code change and no security risk.

Security candidatebuild(core+legacy+crypto): remove deprecated `ECMULT_GEN_PREC_BITS` flagby Roman Zeyde · b5f7bd88 · Oct 30, 2026 · 3 filesMessage 93 · StrongInformational 18Details
Commit message · Roman Zeyde

build(core+legacy+crypto): remove deprecated `ECMULT_GEN_PREC_BITS` flag

It has been removed in https://github.com/bitcoin-core/secp256k1/pull/1058 and released
in https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md#050---2024-05-06.

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

This commit removes an obsolete compiler flag called ECMULT_GEN_PREC_BITS from the build scripts for Trezor's cryptographic code. The upstream secp256k1 library deleted this flag in version 0.5.0, so Trezor is simply cleaning up its build configuration to match. There is no indication this change fixes an active security vulnerability; it is routine build maintenance.

Lower-priorityfix(core): fix build (linker error)by cepetr · 005a137a · Oct 29, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · cepetr

fix(core): fix build (linker error)

[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 candidatedocs(core): changelog for bootloader 2.1.18by obrusvit · 621d7978 · Oct 29, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit

docs(core): changelog for bootloader 2.1.18

[no changelog]

(cherry picked from commit e2b710f84783630ab790993cd9078ec5ee1d3c7c)

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

This commit is purely a documentation update. It moves a bootloader user-interface change note from a pending changelog fragment into the official bootloader changelog for version 2.1.18. There are no code changes and no security implications.

Lower-prioritydocs(core): changelog for prodtest 0.3.10by obrusvit · ac2f2499 · Oct 29, 2026 · 2 filesMessage 72 · AdequateTriage 0Details
Commit message · obrusvit

docs(core): changelog for prodtest 0.3.10

[no changelog]

(cherry picked from commit 3045d5dcdc1c8c98bc1e4b97574efd56d84bdafa)

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Security candidatedocs(legacy): changelog for 1.14.3by obrusvit · ebcec1b8 · Oct 29, 2026 · 4 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit

docs(legacy): changelog for 1.14.3

[no changelog]

(cherry picked from commit a6c65360a4c328c4fcc75294cfec46132e8b1eb7)

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

This commit is purely a documentation update: it moves three changelog entries from draft files into the official CHANGELOG.md for the Trezor legacy firmware version 1.14.3. No code, firmware logic, or security behavior is changed. The listed security items describe changes that were already made in earlier commits and are only being summarized here.

AI review queueddocs(core): changelog for 2.13.1by obrusvit · 75c19c8c · Oct 29, 2026 · 18 filesMessage 72 · AdequateModerate 62Details
Commit message · obrusvit

docs(core): changelog for 2.13.1

[no changelog]

(cherry picked from commit 1c8e894ca5f88fa9789be04eef82f3453af57fc5)

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 · Moderate 62/100

This commit is a documentation-only changelog update for the Trezor firmware 2.13.1 release. It does not change any executable code, but it lists several security fixes that were included in this release: Solana transaction handling improvements, a fix for Unicode characters displaying incorrectly, and warnings for risky xpub exports. Because the commit itself only edits changelog files, the actual security fixes happened in earlier commits that are referenced but not shown here.

Lower-prioritychore: make genby obrusvit · 82b21d5e · Oct 29, 2026 · 1 fileMessage 63 · AdequateTriage 0Details
Commit message · obrusvit

chore: make gen

- should have been done in ece5d6fdc90bc3e66ede31a7bb7d20257f9a0e0e

[no changelog]

(cherry picked from commit 9e77f377cee456186e592b258905db3bda598b1d)

63/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-prioritychore: update releases.jsonby obrusvit · 29422da5 · Oct 29, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · obrusvit

chore: update releases.json

[no changelog]

(cherry picked from commit ece5d6fdc90bc3e66ede31a7bb7d20257f9a0e0e)

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritychore: update definitions timestampby obrusvit · af8ada22 · Oct 29, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · obrusvit

chore: update definitions timestamp

[no changelog]

(cherry picked from commit a8cddfe177b070de6075f6af206ed94305f38aa8)

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Security candidatetest(python): add generation of test attestation certificatesby M1nd3r · a135aa85 · Oct 29, 2026 · 8 filesMessage 87 · StrongInformational 15Details
Commit message · M1nd3r

test(python): add generation of test attestation certificates

- Also, generate test certificates for existing models.

[no changelog]

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
update trust
AI analysis · Informational 15/100

This commit only adds test infrastructure: a script that generates fake attestation certificates for Trezor emulators and copies them into a test directory. The certificates use publicly documented hardcoded debug keys and are used by automated tests. There is no change to production firmware, real device security, or user-facing behavior.

Lower-priorityfix(ci): avoid cloning submodules when starting nix shellby Martin Milata · 557889b6 · Oct 29, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Martin Milata

fix(ci): avoid cloning submodules when starting nix shell

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
documentation-only discount
Lower-priorityfix(core): keep CLI escape state across readsby tychovrahe · fb702022 · Oct 29, 2026 · 2 filesMessage 80 · StrongTriage 0Details
Commit message · tychovrahe

fix(core): keep CLI escape state across reads

- cli_readch() kept the escape sequence parser state in locals, so
a sequence split across reads (ESC in one USB packet, "[A" in the
next) lost its ESC and the rest was inserted as plain text, e.g.
arrow keys in tio printed "[A".
- Move esc_len/esc_code into cli_t and reset them on every returned
character.

[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
Security candidatefix(core): make CLI autocomplete order-independentby tychovrahe · a87f044c · Oct 29, 2026 · 1 fileMessage 85 · StrongInformational 21Details
Commit message · tychovrahe

fix(core): make CLI autocomplete order-independent

- cli_autocomplete() used '\0' both as "no match yet" and as "this
command ends here", so whether Tab stopped at a full name such as
"reboot" or ran on to "reboot-to-bootloader" depended on the order
of the command array.
- Track the first match separately. Seen in the emulator, whose
constructor registration keeps source order; on hardware GCC emits
the section in reverse, which happened to hide it.

[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
Why it was queued
update trust
AI analysis · Informational 21/100

This is a minor bug fix in the command-line interface (CLI) autocomplete feature used inside Trezor devices. When a user typed a partial command like 'reboot' and pressed Tab, the autocomplete behavior could differ depending on the internal order of the command list. In some builds (real hardware) it happened to work; in others (emulator) it could skip past a complete command name and suggest a longer one instead. The fix separates two meanings of the special '\0' character so autocomplete behaves consistently regardless of command order. There is no direct evidence this is a security vulnerability.