At a glance
- The flaw, tracked as LNF-2026-0004, involved how Core Lightning assigned identifiers to payment channels.
- For a firm running Core Lightning, the release number matters: only 26.06.8 covers the closed-channel variant.
- The first attack required no on-chain funding.
Bitcoin's Core Lightning software needed a second security release on Sept. 22 after the July fix for a node-crashing flaw left another attack route open, according to a Nov. 13 disclosure reported by CryptoSlate.
The flaw, tracked as LNF-2026-0004, involved how Core Lightning assigned identifiers to payment channels. Each identifier derives from the Bitcoin transaction output that funds the channel. The software could accept multiple channels referencing the same funding output, producing duplicate records with identical identifiers. Security researcher Nishant Bansal found the handling could be abused to crash the node.
For a firm running Core Lightning, the release number matters: only 26.06.8 covers the closed-channel variant. Version 26.06.6, released July 22, stopped new channels from reusing funding outputs tied to live channels and changed connection handling so stored duplicate records could not trigger the original crash. The September release extended duplicate-identifier checks to closed channels, including channels belonging to different peers.
The first attack required no on-chain funding. A malicious peer could open duplicate pending channels and crash a victim's node by reconnecting. Because the fraudulent channels required no Bitcoin transaction, the attacker paid no transaction fees. Each reconnection could trigger another crash, interrupting payment processing repeatedly.
The persistent variant required on-chain transaction fees and could leave a node unable to recover without a software upgrade. An attacker reused an identifier associated with an already closed channel, then closed another channel carrying the same identifier, producing a failure that survived restarts. Researcher Crypt-iQ independently identified the remaining weakness, prompting the September release.
CryptoSlate reported that the vulnerability could repeatedly crash payment nodes and potentially expose funds held in other channels. The September update also allowed nodes holding previously stored duplicate records to recover without repeatedly crashing.
Reported by the Custody & Infrastructure desk from CryptoSlate. Published . Corrections