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
24896Commits captured
21204AI analyses
60High-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.

21204 analyses
Highest risk·RSS
Moderate 63 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

derive the fee of a wallet transaction from the transactions funding its inputs rather than the value its history entry reports

This commit changes how Sparrow Wallet calculates transaction fees. Previously, the wallet trusted the fee value reported by the Electrum server for each transaction. Now, when the wallet already knows the transactions that fund a given tr…

Server-reported fee no longer trusted blindly when wallet can derive fee from input transactionsFee derivation added in transaction fetch path before wallet stores BlockTransactionNullable fee type introduced to distinguish unknown fees from zero fees
b6d74f80by Craig Raw+176−135 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#4675: Units improvements

This is a routine code-quality and documentation update for the Rust Bitcoin 'units' crate. It adds a few helper methods, improves precision of fee-rate calculations, and updates documentation and warnings. There is no indication of a secu…

No security-relevant signals in commit message or diffChanges are described by author as documentation improvementsNo bounds-checking fixes, no panic fixes, no unsafe code changes
f57f3be6by Andrew Poelstra+206−968 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 100 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(common,core,python,tests): support creating Stellar contracts.

This commit adds support for a new Stellar blockchain feature: creating smart contracts (contract deployment) on Trezor hardware wallets. It extends the messages, layouts, serialization, and tests so users can review and sign Stellar 'crea…

New transaction type support with on-device user confirmationExplicit rejection of unsupported Stellar Asset Contract deployment and legacy CREATE_CONTRACTLength validation on salt (32 bytes) and wasm_hash (32 bytes)
95adcc90by Jun Luo+2385−11229 files
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core/stellar): prepare for contract creation support.

This commit is a routine internal code cleanup in the Stellar cryptocurrency support of Trezor firmware. It renames and moves helper functions, extracts reusable pieces, and adds tests. There is no change to user-visible behavior or securi…

8d312f5cby Jun Luo+144−869 files
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 60 · Adequate
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

do not import wallet descriptors on a cormorant started to test a server connection

This commit fixes a logic bug in Sparrow Wallet's Cormorant feature. Previously, when Cormorant was started only to test a connection to a Bitcoin server (not to actually manage wallets), it could still try to check or import wallet descri…

Missing authorization/state guard: wallet import logic reachable in non-wallet modeUnintended RPC side effects during connection test modePotential wallet descriptor exposure or import against wrong server context
b59f355bby Craig Raw+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 72 · Adequate
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

cancel a retrying connection attempt when testing a server to avoid resource sharing

This commit adds a way to stop an ongoing background server connection attempt when the user tries to test or switch to a different server. Before the change, a retrying connection could keep running in the background while a new test conn…

Resource contention between concurrent/retrying network connectionsPotential denial-of-service or instability from overlapping connection attemptsCleanup of background service before creating a new one
75cd6cebby Craig Raw+16−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 0 · Opaque
MG MAGIC GrantsSkylight Wallet MoneroPrivacy protocolsSoftware wallets

Dark theme

This commit is purely a visual redesign of the app's dark theme. It changes color values—making backgrounds darker and switching accent colors to a Monero orange shade—but does not alter any security logic, data handling, or network behavi…

fe7f552dby Keeqler+38−382 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 0 · Opaque
MG MAGIC GrantsSkylight Wallet MoneroPrivacy protocolsSoftware wallets

New ui

This is a large user-interface refresh for the Skylight Monero wallet. Most changes are cosmetic: new logo, fonts, colors, labels, and screen flows. The only functional security-relevant change visible in the diff is that the app now deriv…

Removal of explicit useSsl toggle in favor of automatic transport derivationShared method-channel rename for secure clipboard (namespace change only)Large UI-only refactor with no visible crypto/storage/network protocol changes
447bb2d7by Keeqler+4851−472063 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 65 AI analysisMessage 35 · Opaque
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

cryptonote_basic: serialization checks

This commit adds stricter limits during deserialization of Monero transactions. It prevents attackers from sending malformed transactions with absurdly large numbers of inputs, outputs, or ring-member references, which could previously exh…

Deserialization-time bounds checking added for container sizesMandatory caps on vin, vout, and key_offsets countsCoinbase input structure enforced during parsing
f8e2a870by j-berman+136−6614 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 50 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

epee: prevent log injection from malformed HTTP headers

This commit removes attacker-controlled HTTP header text from error and debug log messages in Monero's epee networking code. Before the change, a malicious peer or server could put fake log lines, terminal escape codes, or misleading text …

Commit title explicitly states 'prevent log injection from malformed HTTP headers'Multiple log statements changed from printing raw header buffers to printing byte countsBoth client-side response parsing and server-side request parsing paths are touched
90753611by selsta+23−232 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Merge bitcoin/bitcoin#35513: rpc: help metadata fixes

This commit only fixes mistakes and outdated descriptions in the automatically generated help text for Bitcoin Core's remote procedure call (RPC) commands. It does not change what the software actually does, how it processes commands, or h…

fc4f35fdby merge-script+41−477 files
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 77 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet: persist synced metadata and do not sync on load

This Bitcoin Core wallet change makes two related adjustments to how metadata is kept in sync across 'malleated' transaction variants (different versions of related transactions stored in the wallet). First, when metadata is synchronized b…

Wallet metadata consistency changePersistence of previously in-memory-only synchronizationRemoval of load-time metadata repair path
752fd437by furszy+4−42 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 →