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
24877Commits captured
21196AI 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.

21196 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core/delizia): use Marquee in PIN prompts

This commit changes the Trezor hardware wallet's PIN entry screen so that long prompt messages scroll horizontally (like a marquee sign) instead of being cut off. It is a user-interface improvement to handle longer text, such as wipe-code …

90cebdcfby obrusvit+5765−56843 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
ER electrselectrs BitcoinIndexing infrastructureSoftware wallets

Release 0.12.0

This commit is a routine version bump from 0.11.1 to 0.12.0 in the project's package metadata files. It changes only the version number strings in Cargo.toml and Cargo.lock. There is no code change, no bug fix, and no security-related cont…

37501cc4by Roman Zeyde+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 38 · Opaque
ER electrselectrs BitcoinIndexing infrastructureSoftware wallets

Add 0.12.0 changelog

This commit only adds a new section to the RELEASE-NOTES.md file describing version 0.12.0. It lists user-visible changes such as a new indexing dependency, API fixes, a new SECURITY.md file, and routine dependency updates. No program code…

6c763137by Roman Zeyde+8−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core/eckhart): attempts width in PIN keyboard

This commit fixes a layout bug in the PIN entry screen on Trezor's Eckhart hardware model. Previously, the area showing how many PIN attempts remain was given a fixed width of 85 pixels, which could be too narrow for some languages and cau…

No security-relevant code paths modifiedNo input validation, cryptography, authentication, or memory-safety changesUI layout only: text width measurement and area splitting
aac05ac4by obrusvit+709−6932 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#6871: Remove uses of `Index` on `secp256k1::SecretKey`

This is a small code cleanup change in a Bitcoin cryptography library. It replaces an older way of reading secret key bytes with a newer, more explicit method. There is no direct evidence in the commit that this fixes an active security bu…

Touches secret key material (SecretKey bytes)Removes use of Index trait on SecretKey, which upstream secp256k1 considers undesirableNo bounds-checking or validation logic changed
61626a16by Andrew Poelstra+3−32 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): passphrase shown alignment

This commit is a user-interface polish change for Trezor hardware wallets. When a user chooses to reveal the passphrase they are typing, and that passphrase is very long (up to 128 characters), the device now scrolls the text so the most r…

No changes to secret handling, cryptography, memory management, or trust boundariesChange is purely visual/rendering behavior for an already user-visible fieldNo bounds-checking, parsing, or authentication logic is altered
ce266730by obrusvit+119−725 files
No security note in commit
Open full analysis →Source commit ↗
High 79 AI analysisMessage 73 · Adequate
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

Add more guards to amounts being zero or infinity (#3612)

This update fixes a bug where entering special non-number values like 'Infinity' or 'NaN' as a crypto amount could slip past safety checks. Because the wallet treats an amount of zero as 'send everything' (sweep-all), a bad amount that col…

Non-finite double values (Infinity/NaN) accepted by double.tryParse bypass <= 0 amount guardsCollapsed non-finite amounts fall back to Money.zero, which stringifies to the sweep-all sentinel in Monero wallet2New guards reject zero and non-finite amounts before transaction creation
3bb64b71by Omar Hatem+179−119 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6858: base58: saturate the reserve len multiplication

This commit fixes a tiny but real arithmetic bug in the library's base58 string encoder. When asked to reserve memory for an extremely large encoded string, the old code could multiply two numbers together and silently wrap around to a sma…

Integer overflow in buffer-size calculationPotential heap buffer overrun due to undersized allocationRelease-build-only wraparound (debug builds already panic)
aa91cf66by Andrew Poelstra+1−11 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

minor fix [skip ci]

This is a tiny UI timing fix in a cryptocurrency wallet's dashboard screen. It moves a changelog popup so it runs after the current frame is rendered, rather than immediately after a short delay. There is no security-relevant change visibl…

8d75c3f0by Omar+6−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 49 AI analysisMessage 70 · Adequate
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

fix: monero silently ignoring wallet opens (#3621)

This patch fixes a bug where Cake Wallet's Monero module could skip actually opening a wallet and instead leave the user looking at the previously opened wallet without any warning. The old code tracked the 'last opened wallet' path and, i…

State confusion / stale-cache bug: relying on `_lastOpenedWallet` could cause the app to use the wrong wallet objectSilent failure: a wallet open request could return successfully without actually opening the requested walletUI/app-layer integrity issue: user may believe they are operating wallet A while the backend still holds wallet B
6687e478by cyan+54−631 file
No security note in commit
Open full analysis →Source commit ↗
Low 49 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6874: p2p: fix ServiceFlags BitXor semantics

This commit fixes a bug in how the rust-bitcoin library handled the XOR (exclusive-or) operator for Bitcoin network service flags. XOR is supposed to toggle bits on if they are off and off if they are on. The old code incorrectly used a 'r…

Logic bug in bitwise operator semanticsIncorrect use of remove/clear where XOR/toggle was intendedPotential for unexpected protocol behavior if code relies on BitXor to toggle service flags
0de39318by Andrew Poelstra+7−21 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 61 AI analysisMessage 80 · Strong
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

fix: unify encryption across platforms (#3470)

This commit changes how Cake Wallet encrypts and decrypts wallet backup files. It removes an older, weaker encryption method (Salsa20) and switches to a stronger one (XChaCha20) for all platforms. It also adds automatic migration: when the…

Removal of Salsa20 stream cipher for wallet file encryptionAdoption of XChaCha20 via cake_backup libraryAutomatic on-read migration from legacy Salsa20 to XChaCha20
90e25afcby cyan+555−8610 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 →