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
24969Commits captured
21232AI analyses
48High-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.

21232 analyses
Highest risk·RSS
Informational 20 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

fix send to spark name gray screen (nav error)

This commit fixes a UI crash (gray screen) that occurred when confirming a transaction sent to a Spark name. The crash happened because the code tried to read the first recipient address from an empty list. The fix safely checks whether a …

Null-safety / empty-list crash hardening in UI renderingNo change to authentication, transaction signing, validation, or network logicNo external references or vendor security disclosure provided
04ee6496by Julian+10−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 0 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

add comment

This commit only adds a plain-language comment ('# 10 years') next to an existing constant that sets how far in the future a transaction's locktime can be. No code behavior changed.

b2a47fc9by Peter D. Gray+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

simplewallet: rename duplicate amount headers for clarity

This commit only renames two CSV column headers in the Monero wallet's export_transfers output from 'amount' to 'transaction amount' and 'destination amount' to make them less confusing. No numbers, logic, or behavior changed.

08559304by reemuru+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 31 AI analysisMessage 45 · Thin
SW Stack WalletStack Wallet MoneroPrivacy protocolsSoftware wallets

partial revert of SIST in prep for h2 fork

This commit re-enables sending private Firo (Spark) funds to exchange addresses, which had been temporarily blocked. It also upgrades the wallet to support a newer Spark transaction format (Chaum V2) that allows multiple inputs, and it add…

Re-enables previously disabled private Spark-to-exchange sends under the new Chaum V2 rulesAdds explicit guard: multi-input Spark transactions are rejected unless they use the Chaum V2 transaction versionReplaces raw spend version integers with a typed enum to reduce version-confusion bugs
27d00b05by Julian+279−1029 files
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

Merge pull request #10920 from SomberNight/202609_ln_chan_backup_db_upgrade

This commit refactors how Electrum stores Lightning channel backups on disk. It converts backup records from a flexible JSON-style format into a stricter binary format, and adds a one-time database upgrade routine. The change is primarily …

Database migration touches Lightning private key material (privkey, channel_seed, multisig_funding_privkey)Migration masks legacy int16 sign-extension bugs in funding_index, local_delay, remote_delay, port fieldsSerialization format change from JSON StoredObject to custom binary blob
f246d8f7by ghost43+314−317 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 100 · Strong
EP Elements ProjectElements BitcoinBitcoin sidechainsCryptographic librariesNode implementations

Merge ElementsProject/elements#1593: Fix RPC return errors for psbt and invalid rangeproofs

This update fixes several ways that malformed transaction data could crash Elements nodes or trick wallet users into signing bad transactions. The main changes turn internal 'assert' crashes into proper error returns when creating confiden…

assert-to-error conversion in rangeproof generationPSBT explicit output data now required before signing blinded outputspeg-in witness stack length and deserialization hardening
4ddaefc8by merge-script+221−4515 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

tests: db upgrade: add test for convert_version_72

This commit only adds a new automated test. It does not change any production wallet code, fix a bug, or alter how user funds are handled. The test verifies that Electrum can correctly upgrade an old test wallet database containing Lightni…

83115d66by SomberNight+210−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 35 · Opaque
XMR Monero ProjectMonero GUI MoneroPrivacy protocolsSoftware wallets

workflows: fix Windows build

This is a routine GitHub Actions CI fix for the Windows build. It adds the 'rust:p' package to the list of MSYS2 packages installed during the build. There is no security-relevant change visible in the diff.

dc9f980bby selsta+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 60 · Adequate
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

wallet_api: expose signed message verification details

This commit adds a new wallet API function that exposes more details when verifying a signed message, such as which key was used and which signature version was detected. It does not change existing behavior; the old simple true/false chec…

No security-relevant signal: pure API enhancement exposing previously internal verification metadataExisting verifySignedMessage() behavior preserved by returning only the valid flagNo changes to cryptographic verification implementation
5e42addbby selsta+39−44 files
No security note in commit
Open full analysis →Source commit ↗
High 76 AI analysisMessage 68 · Adequate
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Wipe on duress-secret view/activate in Delta Mode

This commit fixes a security bug in the COLDCARD hardware wallet's 'Delta Mode' duress feature. Delta Mode is designed to make the device look normal while silently protecting secrets. Previously, a coercer could force someone to open the …

Missing authorization/safeguard in two secret-revealing flowsDuress/deniability feature bypass allowing secret disclosure under coercionAddition of wipe_if_deltamode() guard to align with other secret-revealing flows
3ad73025by scgbckbone+70−03 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 64 AI analysisMessage 68 · Adequate
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Reject out-of-range txn version on PSBTv2 path

This fix closes a gap where COLDCARD would approve and sign a Bitcoin transaction with an invalid version number if the transaction was packaged in the newer PSBTv2 format. For PSBTv0, such bad versions were already rejected, but the PSBTv…

Missing input validation on alternate code pathSigned output could be non-relayable / invalid on networkRegression test demonstrates pre-patch bypass reached 'OK TO SEND?'
e81b64bbby scgbckbone+21−03 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 45 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Warn for far-future block-height locktime

This change adds a warning when a Bitcoin transaction's locktime is set to a block height more than 10 years in the future. It does not block the transaction but alerts the user, helping catch potential tricks where a transaction is made u…

Adds user-visible warning for unusually distant block-height locktimeDoes not enforce a hard limit; warning-only behaviorTargets potential UI deception / unspendable-funds scenario
4b07fb56by scgbckbone+32−03 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 →