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
24903Commits captured
21206AI analyses
53High-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.

21206 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(tests): reorganize imports - style check

This commit is a minor code cleanup in a test file. It reorganizes Python import statements to follow style guidelines by importing Callable and Sequence from collections.abc instead of typing. There is no functional change and no security…

c67cb289by Vojtěch Nevřela+2−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 36 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

report a transaction tab height the server will not prove instead of marking it unverified until it does

This commit changes how Sparrow Wallet shows a transaction's block height when the connected server cannot prove the transaction is actually in that block. Previously, the transaction tab would label such a height as 'Unverified' while wai…

UI no longer marks a transaction as unverified merely because a proof is still pendingTransaction-tab proof requests now share retry logic with wallet-history proof requestsServer refusals/failures outside any wallet are reported to the user with the same event mechanism as wallet transactions
080be605by Craig Raw+158−639 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #10933 from SomberNight/202609_crandom_prep

This commit is a cleanup change: it creates a single helper module for random-number generation and replaces scattered calls to os.urandom, secrets.token_bytes, and an old randrange helper with the new helpers. The new helpers still use th…

No change to entropy source: still os.urandom / secrets.randbelowNo new dependencies or native codeNo change to key-derivation logic or secret handling
e7ee1e6cby ThomasV+71−4618 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): benqi claim empty property list

This commit only adds a new test case for the Benqi sAVAX redeem function. It includes test data, a small external definition file, and expected screen hashes for automated UI tests. There is no change to production firmware code, no bug f…

fb8a6dddby PrisionMike+48−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): benqi claim empty property list

This commit only updates a single test data file used for Ethereum clear-signing tests. The title says it is adjusting a Benqi claim test case to use an empty property list. There is no code change, no firmware change, and no indication of…

1b355134by PrisionMike+0−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(clear_signing): skip empty property screen

This commit is a minor user-interface fix for Ethereum 'clear signing' flows on Trezor hardware wallets. It simply skips showing a contract-details screen when there are no details to display. There is no indication this is a security fix,…

UI/UX hardening onlyNo cryptographic or authorization logic changedNo bypass of required user confirmation for non-empty data
c7473b71by PrisionMike+24−204 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#36096: rpc: avoid quadratic JSON construction when keys are unique

This change is a performance improvement, not a security fix. It replaces a slow method for building JSON responses in several Bitcoin RPC commands with a faster one. The old method could waste CPU time when returning very large responses …

Performance-only refactor with no semantic change to returned dataNo input validation, memory safety, or authorization changesNo CVE, advisory, or vendor security framing in commit or PR description
51db0e76by merge-script+22−205 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 96 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

Merge bitcoin-core/secp256k1#1928: tests: add coverage for exact-size DER signature serialization

This commit only adds new test code to check that a specific function behaves correctly when given a buffer of exactly the right size. It does not change any production code, fix a bug, or introduce a vulnerability. It is a routine improve…

aa0af2faby merge-script+12−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): st-7789 renamed to i8080

This commit is a simple rename of the display driver from 'st-7789' to 'i8080' because the code supports more than just the ST7789 display controller. It only changes file paths, feature names, and include guards. There is no change to how…

13d2f263by bleska+25−2830 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6840: build(deps): bump taiki-e/install-action from 2.82.7 to 2.82.11

This is a routine update to a GitHub Actions helper used only in automated testing workflows. It changes the pinned version of taiki-e/install-action, which downloads and installs Rust tools like cargo-mutants during CI runs. There is no c…

79482c3cby Andrew Poelstra+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6841: build(deps): bump actions/labeler from 6.1.0 to 6.2.0

This is a routine update to a GitHub Actions workflow that automatically labels pull requests. It bumps the version of the 'actions/labeler' tool from 6.1.0 to 6.2.0. The newer version fixes a minor bug in how pull request numbers are vali…

e0dae5c4by Andrew Poelstra+1−11 file
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 →