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 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump taiki-e/install-action from 2.82.11 to 2.83.2

This is a routine automated update by Dependabot that bumps a third-party GitHub Action used in testing workflows from version 2.82.11 to 2.83.2. It only changes two lines in CI configuration files and does not touch any application code, …

35095071by dependabot[bot]+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 96 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6851: units: Remove amount parsing limit

This commit removes a 50-character limit on strings that can be parsed as Bitcoin amounts. The limit was originally added as a basic defense against denial-of-service (DoS) attacks using very long inputs. The maintainers decided the limit …

Removal of an explicit input-length DoS guardMaintainer statement that the removed limit was intended as DoS protectionNo replacement length limit or mitigation introduced in the diff
563f98f2by Andrew Poelstra+9−786 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core/delizia): switch title/desc in pin popup

This commit fixes a UI wording mix-up on Trezor devices when a user enters a PIN that doesn't match. Previously, the title and description in the 'PIN mismatch' popup were swapped, which could briefly confuse the user about what went wrong…

UI text label swap in PIN mismatch popupRemoval of unused translation key pin__reenter_new_descriptionUpdated UI test fixture hashes for mismatch/failure scenarios
8c5c81b3by obrusvit+208−25613 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core/caesar): use Marquee in ConfirmHS

This commit is a user-interface tweak for the Trezor hardware wallet's Caesar layout. It replaces a static title label with a scrolling 'Marquee' text effect on the homescreen confirmation screen, so long device labels remain readable. The…

74ec8983by obrusvit+49−292 files
No security note in commit
Open full analysis →Source commit ↗
Low 38 AI analysisMessage 45 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

wallet2: filter unchecked RPC error statuses

This commit changes how the Monero wallet handles error responses from the daemon (the network node it talks to). Previously, certain RPC calls used a macro that did not check the daemon's returned status code in all cases. The new code ex…

Unchecked RPC status field previously could allow processing of error responsesReplacement of generic error macro with status-aware error macroDaemon trust setting (m_trusted_daemon) now influences status interpretation
fe371dd7by selsta+5−51 file
No security note in commit
Open full analysis →Source commit ↗
Low 38 AI analysisMessage 50 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

wallet2: validate public node addresses before display

This commit adds validation and formatting fixes for public Monero node addresses shown in the wallet. It prevents invalid or malformed node entries (such as those with port 0 or unparseable hostnames) from being displayed, and it correctl…

Input validation added for externally supplied node host/port dataIPv6 address formatting corrected to RFC 5952 bracketed notationUnderflow guard added for last_seen timestamp subtraction
dab064fdby selsta+20−32 files
No security note in commit
Open full analysis →Source commit ↗
Low 31 AI analysisMessage 50 · Thin
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

wallet2: keep received amount breakdown consistent

This patch changes how a Monero wallet records the breakdown of received amounts when an existing output is 'burnt' and replaced by a new one during transaction processing. It ensures the stored amount list stays consistent with the actual…

Corrects inconsistent accounting of received amounts after a burnt/spent output is replacedAdds a defensive exception for unexpected old/new output valuesNo explicit security claim in commit message or diff
ab343dc8by selsta+7−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 43 AI analysisMessage 68 · Adequate
MJ monero-javamonero-java Cryptographic librariesMoneroSoftware wallets

wallet full: cancel native calls before closing

This commit hardens how the Java Monero wallet shuts down. It makes sure background native (C++) calls are cancelled and finish before the wallet is freed, and it protects listener cleanup from running at the same time as notifications. Th…

Use-after-free / double-free risk in close pathRace condition between native listener callbacks and wallet destructionCross-thread JNIEnv handling in JNI listener destructor
e949b9e1by woodser+123−576 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 45 · Thin
CW Cake WalletCake Wallet / Monero.com MoneroPrivacy protocolsSoftware wallets

change arbitrum default node [skip ci]

This commit changes the default Arbitrum network server used by the wallet from one provider (nownodes.io) to another (publicnode.com), and adds several new decorative icon images. The server change could affect reliability or privacy for …

Default third-party RPC provider changed from nownodes.io to publicnode.comNo cryptographic, authentication, or input-validation code modifiedNo advisory, CVE, or vendor security disclosure referenced in commit message
21c73d00by Omar+422−18 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 61 AI analysisMessage 35 · Opaque
XMR Monero ProjectMonero Cryptographic librariesMoneroNode implementationsPrivacy protocols

common: validate update hashes

This commit fixes how Monero's automatic update checker validates the cryptographic hash of a downloaded update. Previously, the code only checked that the hash string was 64 characters long and contained only letters or digits. That check…

Weak input validation on security-critical hash fieldHash string accepted based on length and alphanumeric check rather than cryptographic parsingPatch replaces manual validation with strict hex-to-hash conversion
928ddfebby Samy+4−51 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Merge rust-bitcoin/rust-bitcoin#6843: Release tracking PR: `internals 0.7.0`

This commit is a routine release-management change. It bumps the version number of the `bitcoin-internals` crate from 0.6.0 to 0.7.0, updates the changelog, and refreshes lock files and dependency declarations across the workspace. There a…

a5310124by Andrew Poelstra+51−4820 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): remove double _colon strings from show_address_details

This commit is a straightforward user-interface string refactor. It moves the colon that appears after labels like 'Account:' and 'Derivation path:' out of the embedded Rust translation strings and into the Python code that calls the addre…

a50eb65eby Michal Kazda+48−1913 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 →