Bitcoin Lightning developers needed two patches to stop a potentially costly attack
A November disclosure shows why July’s repair left a persistent crash route that September’s patch closed. Read the full story on CryptoSlateUnderstand the crypto stories that matter and what to watch next. Get The Catalyst in your inbox
Bitcoin's Core Lightning software required two security patches to eliminate a vulnerability that could repeatedly crash payment nodes and potentially expose funds held in other channels.
A Nov. 13 security disclosure revealed that an initial repair released in July failed to address a second attack method that could keep affected nodes offline even after they restarted.
The vulnerability, tracked as LNF-2026-0004, affected Core Lightning, one of the software implementations used to operate nodes on Bitcoin's Lightning Network.
Security researcher Nishant Bansal discovered that attackers could exploit how Core Lightning assigned identifiers to payment channels, creating duplicate records that caused the software to crash.
The weakness originated in the network's channel-opening process, where each payment channel receives an identifier derived from the Bitcoin transaction output that funds it. Core Lightning could accept multiple channels referencing the same funding output, producing identical identifiers that conflicted with assumptions in its internal software.
In the first attack, a malicious peer could create duplicate pending channels and crash a victim's node simply by reconnecting. The attack required no Bitcoin transaction fees because the fraudulent channels did not need on-chain funding. Each subsequent reconnection could trigger another crash, allowing attackers to repeatedly interrupt payment processing.
However, researchers identified a more persistent variation involving previously closed channels.
By reusing an identifier associated with a closed channel and subsequently closing another channel with the same identifier, attackers could trigger a software failure that persisted across restarts.
Unlike the initial attack, this method required on-chain transaction fees but could leave the node unable to recover without a software upgrade.
Core Lightning developers addressed the original vulnerability in version 26.06.6, released on July 22, after researchers privately reported the reconnection attack earlier that month.
The update prevented new channels from reusing funding outputs associated with existing live channels. It also modified connection handling to prevent duplicate records already stored from triggering the original crash.
However, the protection did not extend to identifiers associated with closed channels, leaving the second attack route available.
Researcher Crypt-iQ independently identified the remaining weakness, prompting developers to introduce broader safeguards in version 26.06.8, released Sept. 22.
The second update expanded duplicate-identifier checks across active and closed channels belonging to different peers. It also allowed nodes containing previously stored duplicate records to recover without repeatedly crashing.