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 small bug-fix patch for Electrum's QML (mobile-style) graphical interface. The crash reporter was not correctly handling exceptions that come from Python's threading system, which could cause the crash reporter itself to misbehav…
Fixes incorrect exception argument handling in crash reporterPrevents potential secondary failure in error-reporting pathNo security boundary crossed; no input from untrusted source is processed
This commit fixes a bug in Electrum's mobile-style QML crash reporter. When an uncaught exception occurred inside a background thread, the crash reporter itself would break because it expected three pieces of information but received one b…
Crash reporter failure could hide or obscure real runtime errors in background threadsNo input validation, privilege boundary, or cryptographic issue presentFix improves diagnostic fidelity but does not close an attack vector
This commit changes how Electrum creates unsigned Bitcoin transactions when an existing 'base transaction' is provided. Previously, the wallet wrongly demanded spendable coins even when the caller supplied a base transaction that already c…
Relaxation of input-source preconditionAddition of consensus-level invariant assertion (at least one input)Addition of empty-input guard before PartialTransaction construction
This commit fixes a crash in Electrum's transaction builder. If a user had only one on-chain coin (UTXO) that was just enough to meet a reserve requirement, clicking 'Max' in the send tab would hit an internal assertion and fail instead of…
Denial-of-service-like crash path triggered by user action in normal wallet stateAssertion failure reachable through GUI send flowFix converts assertion crash into handled NotEnoughFunds exception
This is a routine maintenance commit that updates many of Electrum's software building blocks (dependencies) and raises the minimum required Python version from 3.10 to 3.11. It also refreshes the Linux distribution snapshots used to build…
Dependency version bumps for security-sensitive libraries (cryptography, cffi, libffi, sqlite)Removal of an embedded PGP public key and switch to hash verification for Windows Python installer downloadsBase image refresh from EOL/near-EOL Debian bullseye to bookworm for AppImage builds
This commit is a straightforward internal cleanup: it moves repeated checks like 'are we running on Windows?', 'are we on Android?', and 'are we inside an AppImage?' into a single new helper module called platform.py. The actual behavior o…
This commit is a straightforward internal cleanup: it moves repeated operating-system checks (Windows, macOS, Linux, Android, AppImage) into a single new helper module called platform.py and updates the rest of the code to use those helper…
This commit only changes the software version number from 4.8.3 to 4.8.4 in a single file. It contains no security-related changes, no bug fixes, and no functional code modifications.
This commit relaxes a wallet check when creating a new Bitcoin transaction. Previously, Electrum refused to create a transaction if the user had no spendable coins and no explicit inputs. The change allows creation to continue if a 'base t…
Relaxation of input/coin availability guardAddition of post-construction input count assertionPotential workflow: Replace-By-Fee (RBF) or transaction bumping using base_tx inputs
This commit is a code cleanup in Electrum's mobile-style QML wallet wizard. It replaces an older thread-based background scan for BIP39 seed accounts with a newer asyncio-based task approach, and makes the recovery dialog destroy itself wh…
Refactor of async task lifecycle and cancellation handlingDialog lifecycle cleanup with onClosed: destroy()Use of ignore_if_destroyed to avoid callbacks on destroyed QML objects
This commit is a code cleanup in Electrum's mobile-style QML wallet wizard. It replaces an extra background thread with a simpler asyncio-based callback for scanning BIP39 seed accounts. There is no indication this fixes a security bug; it…
This commit fixes a bug in Electrum's Qt 'Send' tab where selecting a contact from the autocomplete dropdown could briefly leave the wrong recipient active. Previously, the payment field was set to a display name like 'Alice <alice@example…
UI state desynchronization between displayed recipient and active PaymentIdentifierStale PaymentIdentifier usable for ~1 second after recipient text changesPay/Save/Max buttons enabled while recipient is being edited
This commit fixes a UI bug in Electrum's QML (mobile-style) interface where transaction and address labels could become stale or fail to update after editing. It replaces a fragile manual callback system with a proper event listener so the…
No security-relevant signals in diff: no privilege escalation, injection, cryptographic, or authentication changes.Fixes a UI consistency bug (stale labels) that could mislead users but does not enable direct exploitation.Adds event-listener lifecycle management (register/unregister on destroy) to prevent dangling callbacks and potential use-after-free patterns.
This commit fixes a bug in Electrum's mobile-style QML password dialog. If a user tapped the OK/confirm button while the dialog was already closing, the app could emit an extra 'password entered' signal. That extra signal triggered a crash…
Crash in authentication-related code path (AuthMixin)Duplicate signal emission during UI state transitionUser-interaction race condition (tap while dialog closing)
This commit is a performance fix for a wallet function that traces where a transaction's funds came from. It replaces a slow, repeatedly-recursive approach with a more efficient loop and removes an old cache. The change also fixes how the …
Performance fix for wallet history traversalAddress-reuse uncle detection logic changedCache removed in favor of iterative computation
This commit fixes a bug where Electrum wallets created with unusual, hand-crafted 'old-style' seed phrases could not be opened or used. These seeds decode to an odd number of hex characters, which the program previously rejected. The chang…
Input validation relaxed for legacy data (odd-length hex strings)New user-facing error path prevents seed display when mnemonic encoding is impossibleGUI exception handling narrowed: UserFacingException shown as str, other Exception as repr
This commit is a small follow-up cleanup. It translates several user-facing error messages into different languages and makes the Qt GUI handle one specific file-read/write error (StorageReadWriteError) more gracefully, showing a warning d…
Exception-handling path changed in GUIUser-facing error messages internationalizedNo changes to encryption, wallet parsing semantics, or permissions
This commit improves Electrum's error handling when a user tries to open a file that is not a valid Electrum wallet. Previously, if the file contained bytes that were not valid UTF-8 text, the program would crash with a confusing technical…
Error-handling hardeningUser-facing exception message improvedNo cryptographic or parsing logic changed
This is a small user-interface fix in Electrum's Qt desktop app. Previously, if the wallet file was on a read-only folder or an unplugged drive, the app treated the resulting StorageReadWriteError as an unexpected crash and sent a crash re…
No memory safety, cryptographic, or authorization changesException handling change only; no new attack surface introducedCrash-reporting no longer triggered for expected I/O failure scenarios
This commit is a small follow-up cleanup in Electrum's keystore code. It renames an internal helper function, makes the code accept certain unusual 'old' seed phrases that some users created by hand, improves an error message shown to user…
Refactoring of seed validation helperUser-facing error handling improvement in seed displayGrandfathering of non-standard old seed phrases
qt: util.custom_message_box: use explicit RichText instead of AutoText
- InjectNoRichTextEventFilter is changing AutoText to PlainText, and that also affects the internal QLabel inside the message box
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritySECURITY.md: ask people to say how they want to be credited asby SomberNight · 0a46cf82 · Sep 15, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · SomberNight
SECURITY.md: ask people to say how they want to be credited as
55/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathboot or update path
AI analysis · Low 37/100
This commit makes the Electrum desktop wallet explicitly tell its Qt GUI widgets to interpret certain text as rich HTML-like text, rather than leaving it on the automatic/default setting. In recent Qt versions, the default behavior changed so that labels with link tags or HTML may no longer render as clickable rich text unless the application opts in. The patch is defensive: it ensures user-facing labels (help text, warnings, update notices, transaction details, seed warnings, etc.) continue to display formatted text and clickable links correctly. There is no direct evidence in the diff of an exploitable vulnerability being fixed; it reads more like a compatibility/adjustment change after a Qt behavior change. One label was also converted from HTML line breaks to plain-text line breaks, which slightly reduces HTML parsing exposure.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 11/100
This commit adds explicit 'RichText' formatting markers to several user-interface text labels in Electrum's QML (mobile-style) GUI. Previously these labels may have implicitly rendered HTML-like tags. The change is a cleanup/adaptation to newer Qt behavior and does not, on its own, introduce a security vulnerability. It is not a fix for a known exploit, but it touches code that handles rich text rendering, which can be security-relevant if untrusted strings are later inserted.
Lower-priorityqt: set textFormat=PlainText for all QLabels dynamicallyby SomberNight · 03c9cb13 · Sep 14, 2026 · 1 fileMessage 81 · StrongTriage 0Details
Commit message · SomberNight
qt: set textFormat=PlainText for all QLabels dynamically
You have to opt-in to rich text if you want it for your label! Upstream chose convenience-by-default for their GUI framework. Shame. :)
-----
earlier, less satisfactory attempt: ``` def eventFilter(self, obj: QObject, event: QEvent) -> bool: if not isinstance(event, QtCore.QChildEvent): return False # - ChildAdded event: already constructed QWidget gets parented # - note: does *not* fire if parent gets set at construction time, e.g. Label("", parent=self) # - ChildPolished event: # - see https://doc.qt.io/qt-6/qstyle.html#polish : # > This function is called for every widget at some point after it has been fully created # > but just before it is shown for the very first time. if event.type() not in (QEvent.Type.ChildAdded, QEvent.Type.ChildPolished): return False child = event.child() if not isinstance(child, QLabel): return False if child.textFormat() != Qt.TextFormat.AutoText: # non-default textFormat => we leave it alone return False child.setTextFormat(Qt.TextFormat.PlainText) return False ```
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI review queuedMerge pull request #10940 from accumulator/fix_10937by Felix · a57ef6e7 · Sep 14, 2026 · 10 filesMessage 73 · AdequateModerate 62Details
Commit message · Felix
Merge pull request #10940 from accumulator/fix_10937
Add BOLT11DecodeException and InvalidBitcoinURI wraps for missing uncaught exceptions.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 62/100
This commit tightens how Electrum parses Bitcoin payment requests (BOLT11 lightning invoices and BIP21 URIs). It turns previously uncaught internal errors into proper validation failures, rejects malformed invoice fields that used to be silently skipped, and adds a wallet database upgrade that deletes stored invoices which no longer pass the stricter checks so old wallets can still open. The main user-visible risk is that a malicious or malformed invoice/URI could previously crash the parser or be accepted when it should have been rejected.
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 40/100
This commit tightens how Electrum parses BOLT11 Lightning invoices. It now rejects duplicate 'n' (node pubkey) tags instead of silently keeping only the first one, and it rejects invoice timestamps that are negative or too far in the future. These are defensive correctness fixes that reduce the chance a malformed or malicious invoice could confuse the wallet, but they are follow-up cleanups rather than a fix for a known active attack.
Lower-priorityMerge pull request #10967 from fametrano/btclib-qml-test-locale-leakby Felix · 1444e34c · Sep 14, 2026 · 1 fileMessage 83 · StrongTriage 0Details
Commit message · Felix
Merge pull request #10967 from fametrano/btclib-qml-test-locale-leak
tests: qml: restore the process locale after each QETestCase
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
merge-commit duplicate discount
Lower-prioritytests: qml: restore the process locale after each QETestCaseby Ferdinando Ametrano · a89c52c9 · Sep 13, 2026 · 1 fileMessage 95 · StrongTriage 0Details
Commit message · Ferdinando Ametrano
tests: qml: restore the process locale after each QETestCase
QETestCase.setUp() starts a thread that constructs a QCoreApplication, and Qt sets the process locale from the environment while doing so. tearDown() only exits the application, so that change outlives the test case: tests running afterwards format dates and numbers in the environment's locale rather than in the one the interpreter started in.
pytest collects tests/qml/test_qml_qeconfig.py, a QETestCase, before tests/qml/test_qml_qetransactionlistmodel.py, which is not one. On a machine whose environment locale is Italian, the latter's test_format_date_by_section then fails on the strftime('%a, %H:%M') it asserts:
AssertionError: 'gio, 14:30' != 'Thu, 14:30'
and passes when that file is run on its own. CI does not see it, its runners using a C.UTF-8 locale in which '%a' renders identically before and after the leak.
Record the locale in setUp(), before the Qt thread starts, and restore it from a cleanup. unittest runs cleanups after tearDown(), so the locale goes back once the application has exited and its thread has been joined. Restoring it as soon as the application is constructed would instead put Qt, for as long as it runs, back into a locale it had just overridden for itself: under LC_ALL=C it moves LC_CTYPE to UTF-8 and reports that it did. A cleanup also covers a subclass whose own setUp() raises, where tearDown() never runs at all, and a failure to restore is then reported beside the test's own outcome instead of in place of it.
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
This commit fixes a shutdown bug in Electrum's hardware wallet support. Previously, if disconnecting from a hardware wallet failed, the cleanup thread could keep running, which could crash the application when closing. The fix stops the thread before attempting disconnect, and makes the disconnect step tolerate errors instead of crashing.
Merge pull request #10958 from SomberNight/202609_deps
build: update some dependencies
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
This commit is a routine dependency update for the Electrum Bitcoin wallet. It bumps versions of Python, OpenSSL, secp256k1, and various Python packages used in builds and runtime. The commit itself does not fix any known security bug in Electrum's own code, nor does the project describe it as a security update. Dependency updates can indirectly improve security by including upstream bug fixes, but without specific vulnerability information we cannot say this patch is itself a security fix.
Merge pull request #10965 from SomberNight/202609_header_checkpoints
update block header checkpoints
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 21/100
This commit only adds new Bitcoin block header checkpoints to Electrum's built-in chain data files. Checkpoints are hardcoded reference points that help the wallet verify it is following the real blockchain and not a fake one. Updating them is a routine maintenance change; it does not fix a software bug and does not introduce new code behavior. It slightly strengthens protection against certain long-range attacks by extending the known-good chain history.
``` >>> network.export_checkpoints(f"/home/user/wspace/electrum/electrum/chains/{electrum.constants.net.NET_NAME}/checkpoints.json") ``` (with the last 1-3 retarget periods manually removed, depending on how much we trust a chain not to do deep reorgs)
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply refreshes Electrum's built-in list of Bitcoin blockchain checkpoints. Checkpoints are known-good block hashes that help the wallet verify it is following the real chain. The update adds newer checkpoints for mainnet, signet, testnet, and testnet4. There is no code change and no security vulnerability introduced or fixed here.
lnworker: fix inflight payment detection for startup case too
Similar to prev commit. This considers more HTLCs to be "inflight" now, as it also includes ones where removal started but is not yet irrevocably committed yet.
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context