Bitcoin
Security advisory details the funding flaw fixed in Core Lightning
Advisory LNF-2026-0004 explains how duplicate channel IDs could stop a Core Lightning node. The complete fix was already available in version 26.06.8, released in September.

The November 13 advisory revisits a September fix
On November 13, 2026, Nishant Bansal published an advisory on a flaw in Core Lightning, one of the programs used to operate a node on Bitcoin’s Lightning Network. He presented his findings on Delving Bitcoin the following day. He rated the denial-of-service flaw as high severity and said the complete fix has been available since version 26.06.8, released on September 22. The advisory describes two situations that could interrupt a node’s operation.
The flaw concerned channels whose identifiers are derived from a Bitcoin transaction output used to fund them. Two channels should not share the same identifier. According to the advisory, some software versions could nevertheless record two channels associated with the same output. The issue could surface later because Core Lightning components relied on that identifier to find the channel to process. The first public report, on July 2, concerned the acceptance of two channels with the same identifier. The researcher says he subsequently confirmed the impact on node availability in testing.
Two different effects on node availability
In the first case Bansal describes, the node could stop when a peer reconnected if two channels shared an identifier. The software tried to associate two channels with the same communication process and hit a stop condition. The duplicate entries remained in the local database after restart. Bansal says the crash could therefore recur each time the relevant peer reconnected.
The second case, reported separately to Core Lightning by the researcher Crypt-iQ, involved a channel that had already closed. A duplicate could then trigger a crash when another channel closed, followed by a series of failed restarts. According to Bansal, an unavailable node can miss events on the Bitcoin chain that require a response within a deadline to protect funds in its other channels. The advisory describes this risk without establishing an observed loss.
Version 26.06.8 addresses both cases
The advisory author gives the general affected range as versions 0.12.0 through 26.06.7, with differences between the two cases. Version 26.06.6 already included the reconnect fix. Version 26.06.8 extended the checks to identifiers used by closed channels and changed how previously stored duplicates are handled. The software can reject a new conflict while handling local state inherited from older versions.
The project’s release notes and the advisory distinguish the fix timeline from the public disclosure timeline. Version 26.06.8 is the first reference point for both variants described. The advisory author recommends that node operators use the latest Core Lightning release to benefit from fixes published after September as well.
