A Nov. 13 security disclosure showed that Bitcoin's Core Lightning software required two patches to remove a vulnerability that could repeatedly crash payment nodes and potentially put funds in other channels at risk.
The issue, tracked as LNF-2026-0004, affected Core Lightning, one of the software implementations used to operate nodes on the Lightning Network. Security researcher Nishant Bansal found that attackers could exploit how the software assigned identifiers to payment channels, creating duplicate records that caused crashes.
Duplicate identifiers and repeated crashes
The weakness began in the 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 one attack, a malicious peer could create duplicate pending channels and crash a victim's node by reconnecting. The attack required no Bitcoin transaction fees because the fraudulent channels did not need on-chain funding. Each reconnection could trigger another crash, allowing attackers to repeatedly interrupt payment processing.
Researchers also identified a more persistent variation involving previously closed channels. By reusing an identifier associated with a closed channel and then closing another channel with the same identifier, attackers could trigger a software failure that persisted across restarts. Unlike the first method, this route required on-chain transaction fees but could leave a node unable to recover without a software upgrade.
Why the first patch was incomplete
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 and modified connection handling to prevent stored duplicate records 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.
Operational and financial risk
According to the advisory, nodes forced offline could lose the ability to monitor Bitcoin's blockchain for attempts to settle channels using revoked transaction states. That could allow dishonest counterparties to claim funds using outdated channel balances. Offline nodes could also miss deadlines for collecting time-sensitive payments, placing Bitcoin held in unrelated channels at risk.
The researchers did not report confirmed exploitation or financial losses.
The findings affect Core Lightning versions preceding the complete September repair, with the reconnection vulnerability dating back to version 0.12.0 and the persistent closed-channel crash introduced in version 25.05. Developers have since released additional security updates, including version 26.06.10, which addresses other vulnerabilities involving channel operations, payment resolution, and remote crashes.
Core Lightning's maintainers have urged operators to upgrade to the latest release to protect their nodes against the disclosed weaknesses.


