Continuous public-repository analysis

Open source.
Not open secrets.

We watch what security-critical projects change—then translate the code into clear, independent intelligence anyone can understand.

36Projects watched
27612Commits captured
22440AI analyses
57High-risk findings · 30d
Active security advisories
Critical

LNbits 1.7.0: urgent theft-risk security update

LNbits says every version before 1.7.0 is affected by the vulnerability discovered November 8 and that funds on prior versions are at risk of being stolen. Version 1.7.0 contains incident-response security fixes, but the vendor has not yet published full exploit details.

Affected: All LNbits versions before 1.7.0. The warning is no longer limited to servers using the Paywall extension. Credentials or secrets exposed before an upgrade may continue to give an attacker access afterward.

Action: Keep older instances stopped and upgrade to 1.7.0 before running LNbits. If compromise is suspected, preserve logs and prefer a fresh server. Reset all wallet keys, rotate funding-source credentials and every other stored secret, and recreate extension and application connections with new credentials. Review balances and outgoing payments.

Read source ↗
Critical

Electrum 4.8.3: malicious-server RBF theft in the wild

Electrum confirms malicious servers are exploiting a transaction-replacement attack in the wild. A server can suppress a user's newly broadcast transaction, substitute an invalid conflicting transaction paying a lookalike attacker address, and cause Electrum to display it. If the user manually fee-bumps that transaction, the wallet can sign the attacker's replacement. Electrum reports two victims and one confirmed loss of funds.

Affected: Electrum versions before 4.8.3 when connected to an untrusted or malicious Electrum server. Users who connect only to a server they trust, such as their own server, are not affected according to the vendor.

Action: Upgrade to Electrum 4.8.3 immediately, download only from electrum.org, and verify the release signatures. Until upgraded, do not fee-bump an unexpected or substituted transaction and verify every output address and amount before signing any transaction.

Read source ↗
Critical

Core Lightning v26.06.9: urgent loss-of-funds security update

Core Lightning says v26.06.9 fixes a newly reported vulnerability that can lead to loss of funds. The release also contains security fixes in channel reestablishment, splicing, HTLC shutdown handling, onion and on-chain handling, gossip range queries, runes, configuration, and several remote-crash and hardening fixes.

Affected: Every Core Lightning node running v26.06.8 or earlier is affected, according to the vendor. Technical tests for the security fixes are temporarily withheld to slow exploit development while operators upgrade.

Action: Upgrade to Core Lightning v26.06.9 immediately. Download the release from https://github.com/ElementsProject/lightning/releases/tag/v26.06.9, verify the appropriate signed SHA256 manifest and checksums for your architecture, install it, restart lightningd, and confirm the running version.

Read source ↗
The watch feed

Changes worth understanding

AI analysis is published as generated. Community notes appear after human validation.

22440 analyses
Highest risk·RSS
Informational 20 AI analysisMessage 81 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

Fix address search to match address or label case-insensitively (#3837)

This commit fixes a user-interface bug in the wallet's address search. Previously, searching for an address sometimes returned no results if the address contained uppercase letters (common for Zcash, Ethereum, Solana, Tron) because the sea…

e0981df1by claude[bot]+5−52 files
No security note in commit
Low 29 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

request bitcoin core wallet spends in batches from v28 when starting cormorant and wait for the initial load before polling

This commit improves how the Sparrow Wallet desktop app talks to a self-hosted Bitcoin Core node when using the built-in 'Cormorant' connection. It batches transaction lookups on newer Bitcoin Core versions, waits for the initial wallet hi…

Avoids redundant full-wallet history requests during initialization, reducing load and potential race conditionsAdds batch JSON-RPC response parsing, fixing possible parsing failures on batched gettransaction callsImproves error-message accuracy for Tor/proxy connections to prevent misdiagnosis of connection failures
1356b2ccby Craig Raw+354−124 files
No security note in commit
Low 47 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

upgrade tern to v1.1.2 and use it for bitcoin core rpc and paynym avatar requests

This commit upgrades an internal networking library called 'tern' and switches Bitcoin Core RPC, PayNym avatar, and Payjoin requests to use it. The change is mostly a refactoring to consolidate HTTP handling, fix proxy-switching races, and…

Replaced infinite HttpURLConnection timeouts with explicit 15s/60s connect and 10s idle timeoutsAdded synchronized proxy update path to prevent use of stale Tor proxyAdded Closeable lifecycle to BitcoindTransport so connections are closed on stop/initialization failure
96c3ef69by Craig Raw+868−14914 files
No security note in commit
Low 29 AI analysisMessage 50 · Thin
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Merge remote-tracking branch 'agent/benma-agent/checked-rust-translations'

This commit hardens how translated user-facing messages are selected in the BitBox02 hardware wallet firmware. It introduces compile-time checks that reject messages missing from the English translation catalog and that verify the number o…

Compile-time validation of translatable strings against source locale catalogCompile-time validation of format placeholder count against argument array lengthClippy lint disallows direct use of unchecked translation/format functions
1db22746by Marko Bencun+221−6915 files
No security note in commit
Low 45 AI analysisMessage 61 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

release 3.2.2 (#2327)

This is a routine firmware release (version 3.2.2) for the Keystone 3 hardware wallet. The main user-visible change is adding support for the Zcash NU7 network upgrade. The code changes mostly update Zcash-related Rust libraries to newer v…

Zcash dependency major-version upgrades and API migration for NU7 compatibilityLock-screen countdown timer now initialized to NULL and explicitly stopped on label deletion, reducing dangling-timer riskTransaction-check-fail signal fixed to pass correct struct size instead of pointer size
08150faeby github-actions[bot]+1032−90129 files
No security note in commit
Low 49 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: disable paid reviews (#4325)

This update turns off a default paid-extension review service in LNbits. It stops the wallet from automatically contacting a third-party payment/review server when it lists or updates extensions, and resets the default review URL to empty.…

Default third-party review/payment URL removedMigration forcibly resets stored review URL to emptyBackground extension update/install no longer queries remote pay_link for pricing
77cc2276by Vlad Stan+208−1313 files
No security note in commit
Low 34 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update NuGet dependencies and compatibility

This commit updates many third-party software libraries (NuGet packages) to newer versions and makes small code adjustments so BTCPay Server stays compatible with those updates. The most notable security-relevant change is a rewrite of the…

Dependency version bumps for libraries with known security maintenance value (HtmlSanitizer, Fido2, MailKit, Microsoft.AspNetCore, System.Security.Cryptography.Pkcs)Manual CSV field escaping added to prevent formula/CSV injection in wallet transaction exportsFido2 configuration/AppID handling changed during Fido2 library upgrade
bef0935cby Alfred+55−4411 files
No security note in commit
Informational 21 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

order block transaction references consistently for any height

This commit changes how Sparrow Wallet sorts wallet transactions by block height. It replaces a manual subtraction-based height comparison with a dedicated comparison method. The change is likely intended to fix subtle sorting bugs—especia…

Integer subtraction used for comparison can overflow if heights differ widely or use sentinel values, producing incorrect sort orderInconsistent ordering between `TransactionEntry` and `WalletTransactionsEntry` could break balance calculations or UI consistencySubmodule bump suggests the real fix lives in an external dependency and is not visible in this diff
fb0e5856by Craig Raw+5−115 files
No security note in commit
Low 48 AI analysisMessage 45 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

upgrade pgpainless to v1.7.8

This commit updates the PGP verification library used by Sparrow Wallet and tweaks the logic that decides when a downloaded release file is considered valid. The code change makes the app less likely to wrongly disable manifest verificatio…

Dependency upgrade of a cryptographic library (pgpainless)Logic change in signature/verification flowPotential bypass of manifest verification when release content equals signature content
62b2f7edby Craig Raw+11−83 files
No security note in commit
Moderate 57 AI analysisMessage 45 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

upgrade flyway to v13.12.1

This commit upgrades the Flyway database-migration library inside Sparrow Wallet from version 9.22.3 to 13.12.1 and rewrites the wallet-file validation code. The old validator inspected raw bytes of the H2 database file for suspicious keyw…

Major dependency upgrade with accompanying defensive-code rewriteReplacement of negative-pattern DDL filtering with strict positive-pattern DDL allow-listAddition of H2 MVStore type-registry and undo-log validation
2529bd74by Craig Raw+316−695 files
No security note in commit
High 76 AI analysisMessage 81 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Merge PR 'Fix HTLC loss when a closed channel's ID is reused in open_channel' (#5562)

This patch fixes a bug in the Lightning Dev Kit where a forwarded payment (HTLC) could be permanently lost if a new channel reused the same temporary ID as a recently closed channel. Previously, the code could look up the new, unfunded cha…

Loss of forwarded HTLC preimage persistenceTemporary channel ID reuse collisionClosed ChannelMonitor update path bypass
7ac88a11by Matt Corallo+109−22 files
Vendor flagged security relevance
01
Why commit watching?

Security should leave a paper trail.

A quiet fix may be responsible caution—or it may leave users unaware that their assets were ever at risk. CommitWatch preserves the evidence, adds context, and tracks whether vendors disclose, acknowledge, and learn.

Why we built this →