Core Lightning Needed Two Patches to Close a Node-Crashing Flaw

In this article
Core Lightning, one of the software implementations used to run Bitcoin’s Lightning Network, required two separate security releases to eliminate a flaw that could repeatedly crash payment nodes and leave them unable to restart, according to a security disclosure dated November 13, 2026 and reported by CryptoSlate. The flaw is tracked as LNF-2026-0004 and was identified by researcher Nishant Bansal.
How the duplicate-identifier flaw worked
Each Lightning channel receives an identifier derived from the Bitcoin transaction output that funds it. Core Lightning could accept more than one channel pointing at the same funding output, producing identical identifiers that conflicted with assumptions built into the software’s internal logic.
In the first method, a malicious peer created duplicate pending channels and crashed a victim’s node by reconnecting. No fee was needed because those channels were never funded on-chain, and each reconnect could trigger a fresh crash. A second method reused an identifier tied to an already-closed channel; when another channel with the same identifier was closed, the software failure persisted even after a restart.
The first patch, merged July 16 and shipped in v26.06.6 six days later, stopped new channels from reusing funding outputs already held by that peer’s live channels. It also replaced an assertion in connection handling with defensive treatment of duplicate records already stored. What it did not do was extend the outpoint lookup to closed channels.
Version 26.06.8 widened the check to channel identifiers across every peer’s live and closed channels, covered both funder and dual-funding paths, and allowed already-stored duplicates to load and then close instead of looping. A later release, v26.06.10, addressed separate issues in channel operations, payment resolution and remote crashes.
Why it matters
A node that can be kept offline loses its ability to watch the chain for attempts to settle channels using revoked transaction states, and the advisory warns this could let a dishonest counterparty claim funds from an outdated balance. Offline nodes can also miss deadlines for time-sensitive payments, putting Bitcoin held in unrelated channels at risk.
The disclosure sits alongside a separate Lightning fix covered in our report on Lightning force-close costs and the multi-day wait for locked funds, which shows how routine recovery operations already carry real cost and delay for node operators. Researchers did not report confirmed exploitation or losses in this case, meaning the exposure is theoretical for anyone who stayed current but real for those who did not. The reconnection flaw dates back to version 0.12.0, while the persistent crash was introduced in version 25.05.
What to watch
The advisory and related developer discussion recommend running the latest Core Lightning release rather than stopping at v26.06.8, and maintainers have urged operators to upgrade as soon as practical. The next checkpoint is how many nodes remain on versions before the September patch, and whether any operator reports the restart loop in the wild.
Market snapshot
Bitcoin traded at $64,820 (₹6,059,090) on November 18, 2026, up 0.3% over 24 hours but down 11.6% over seven days, with market capitalisation of $1.30 trillion and $22.14 billion in 24-hour volume, according to CoinPaprika data captured at 01:16 UTC. This article is not financial advice; crypto markets are volatile and prices can change rapidly.
Source: CryptoSlate





