# Core Lightning Needed Two Releases to Close a Channel Crash Flaw

By Simon Yoon

Canonical URL: https://www.tokenpost.com/news/technology/59758
Published: 2026-11-17T18:54:42.000Z
Updated: 2026-11-17T18:54:42.000Z
Section: Technology

> A July update stopped one attack route, but a route involving closed channels remained until a September release.

Core Lightning needed two software releases to fully close a flaw that could repeatedly crash a node and leave it unable to monitor other payment channels on Bitcoin’s Lightning Network.

Researcher Nishant Bansal’s advisory, dated Nov. 13, described the flaw; his public forum post was dated Nov. 14. The issue affected Core Lightning versions v0.12.0 through v26.06.7. In the channel flow involved, an identifier derives from a channel’s funding outpoint. Reusing an outpoint for two channels could give them the same identifier.

In one attack route, an attacker could create duplicate pending channels and crash a node when reconnecting. The route required no on-chain fees and could be repeated after each restart. Core Lightning released v26.06.6 on July 22 at 12:16 p.m. ET (16:16 UTC). The update blocked a peer from reusing an outpoint among its live channels and changed reconnect handling so duplicate records already stored would not trigger the same failure.

A separate route involved an outpoint associated with a closed channel. Closing another channel with the same identifier could trigger a crash loop that continued across restarts without further action by the attacker. This documented route required on-chain fees. Core Lightning released v26.06.8 on Sept. 22 at 9:38 a.m. ET (13:38 UTC), expanding identifier checks across live and closed channels and allowing existing duplicate closed-channel records to load and close.

A node that remains offline may miss blockchain events that help protect funds in its other channels, including a revoked channel commitment or a time-sensitive payment claim. The disclosure provided no count of affected nodes or confirmed losses.

Bansal urged operators to update: “Users should upgrade to the latest release to protect their nodes.”


