CommitWatch RSS
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.

Explore the watch feed ↓See how scoring works →
34Projects watched
24634Commits captured
21070AI analyses
58High-risk findings · 30d
Active security advisories
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 ↗
Critical

Liquid Network: ~4,000 BTC withdrawn in critical peg incident

Liquid confirms that purported white-hat actors withdrew roughly 4,000 BTC (about $320 million) from its federation wallet through the SideSwap PAK. Liquid says the PAK and other federation keys were not compromised. The actors have not yet returned the funds. Independent public analysis points to a newly introduced range-proof cache-key flaw, but Liquid has not yet published its root-cause report.

Affected: The L-BTC peg and Liquid federation reserves are affected. Bridge nodes are disabled, the sidechain is paused, and exchanges have suspended L-BTC deposits and withdrawals. Liquid says other issued assets, including USDT, DePix, and RWAs, are unaffected; Bitcoin's base layer is not affected.

Action: Do not initiate Liquid peg-ins, peg-outs, swaps, or L-BTC exchange deposits or withdrawals while the network is paused. Follow official Liquid and Blockstream updates, and treat L-BTC peg exposure as impaired until reserves are restored and a verified fix and incident report are published.

Read source ↗
Critical

BTCPay Server: actively exploited LND credential theft

BTCPay confirms that an unauthenticated remote attacker could obtain LND .macaroon credentials, take control of affected LND nodes, and move funds. The vendor reports confirmed exploitation and stolen funds.

Affected: BTCPay Server versions before 2.4.2, including 2.4.2 release candidates, when used with LND. BTCPay says other Lightning implementations are not exposed to this specific credential risk.

Action: Update to BTCPay Server 2.4.2 and LND 0.21.1 immediately, review node activity, and rotate credentials. If you cannot update now, take the affected server offline.

Read source ↗
The watch feed

Changes worth understanding

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

21070 analyses
Highest risk·RSS
Low 44 AI analysisMessage 68 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #10987 from spesmilo/fix_10986

This commit fixes a bug where Electrum failed to recognize certain already-signed Bitcoin transactions as complete. Specifically, for native SegWit inputs, Bitcoin Core can produce a finalized PSBT with a valid witness but an empty scriptS…

Logic error in transaction completeness detectionNative SegWit witness handling edge casePSBT interoperability issue with Bitcoin Core
bef80421by ghost43+11−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
XMR Monero ProjectMonero GUI MoneroPrivacy protocolsSoftware wallets

p2pool v4.18.1

This commit simply updates the Monero GUI wallet's built-in downloader to fetch a newer version of the bundled P2Pool mining software (from v4.18 to v4.18.1) and updates the matching file hashes. There is no indication in the commit itself…

8d95b8a4by SChernykh+12−121 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1840: ci: Simplify module configuration and extend test coverage

This change only edits the project's automated continuous-integration (CI) configuration file. It turns on all optional cryptographic modules by default in CI and adds test runs that disable each module one at a time. There is no change to…

No source-code changesNo build-system logic changesCI-only workflow refactor
9701113fby merge-script+29−1001 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 50 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

fuzzing: Update manifest and seed corpus generation

This commit only updates the fuzzing test harness: it adds a new source file to the fuzzing manifest and expands the seed corpus generator with test cases for BIP-370 lock-time handling. There are no changes to the actual application code …

New fuzzing coverage targets locktime validation logic in preprocess_inputs.cSeed corpus includes boundary and mixed-input locktime casesNo application/firmware code changes present in the diff
7c1efc49by Salvatore Ingala+48−02 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 63 AI analysisMessage 83 · Strong
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

net: detect half-closed sockets before connection reuse

This patch fixes a connection-reuse bug in Monero's networking helper. Previously, the client could reuse a TCP connection that the peer had already half-closed (for example, after sending data and shutting down its send side). That could …

Half-closed / EOF socket reuseTLS close_notify not checked before connection reuseIdempotent disconnect to avoid repeated TLS shutdown / exceptions
bb8f10c4by Guoqiang Liu+685−95 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 59 · Thin
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

remove old ui (#3629)

This is a large cleanup commit that removes the old user interface code from the Cake Wallet app and switches the app to use only the new UI. It deletes many old screens, view models, fonts, and related dependency-injection registrations. …

Large-scale deletion of legacy UI code and unreachable routesRemoval of disabled/unused Yat emoji-id integration code (commented-out network calls and empty URL constants)Removal of old buy/sell webview pages that handled external payment flows
d38c7481by malik1004x+74−18935155 files
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core/embed): add missing memzero to modtrezorcrypto

This commit adds secure cleanup (memzero) and fixes memory allocation ordering in Trezor's cryptocurrency module. It ensures that sensitive key material, such as BIP-32 and Cardano secrets, is wiped from memory even when an error occurs du…

Sensitive key material cleanup with memzero added to error and success pathsMemory allocation reordered to allow proper object deletion on failureIntermediate Cardano derivation secrets are now explicitly zeroed
03368424by M1nd3r+22−62 files
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 90 · Strong
BB BitBoxBitBox02 firmware BitcoinHardware wallets

build: unify product and probe commands

This commit is a developer-facing build-system refactor. It replaces many hard-coded Make targets with a single saved configuration (product, board, edition, debug mode, probe tool) and adds Python helper scripts to build, flash, and debug…

New developer tooling controls how bootloader/firmware ELFs are flashed and how GDB initializes device state (VTOR/SP/PC/xPSR).BitBox03 factorysetup is intentionally loaded into RAM and resumed without reset; a script bug could leave the device in an unintended state.J-Link Commander flash script is generated in a temporary directory and uses quoted paths; path-quoting bugs are a potential, though low-severity, issue.
ee0a1e41by Niklas Dusenlund+932−57028 files
No security note in commit
Open full analysis →Source commit ↗
Low 31 AI analysisMessage 58 · Thin
AQ ACINQEclair BitcoinLightning Network

Use bitcoin-kmp 0.49 (depends on bitcoin-kmp 0.32.0 and secp256k1-kmp 0.24.0) (#3362)

This commit updates Eclair's Bitcoin library dependency from version 0.48 to 0.49, which internally uses newer versions of bitcoin-kmp and secp256k1-kmp. The code changes only replace old property accesses (like `.txid`) with new method ca…

Dependency version bump for Bitcoin and secp256k1 cryptographic librariesSource changes are API adaptations (.txid -> .getTxid), not logic changesSecurity-critical validation code is touched (PSBT/transaction integrity checks against malicious Bitcoin Core)
6162e2aaby Fabrice Drouin+22−44 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 70 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

Firmware v9.25.0 verification

This commit adds two digital signature files to the repository. They are third-party reproducible-build attestations (assertions) for the already-released BitBox02 firmware version 9.25.0. The commit does not change any firmware source cod…

b454a627by Yasser Aziza+0−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 88 · Strong
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Add functional tests for the BIP-370 lock time derivation

This commit only adds new automated tests for how the Ledger Bitcoin app chooses a transaction's lock time when signing a PSBTv2. It does not change the app's actual signing code. The tests verify that the app derives the expected lock tim…

ab7131cbby Salvatore Ingala+247−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 60 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Unit tests for PSBTv2 locktime fields, and nLocktime calculation

This commit only adds new automated tests for how the Bitcoin app figures out transaction lock times from PSBTv2 data. It does not change the actual app logic, so by itself it cannot introduce a security bug or fix one. The tests are defen…

Tests target lock-time consensus rules and PSBTv2 field parsing, which are security-sensitive areasTests explicitly cover error-path behavior and state immutability on failureNo changes to firmware, signing flow, or cryptographic code in this commit
c1453b81by Salvatore Ingala+466−23 files
No security note in commit
Open full analysis →Source commit ↗
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 →