Core Lightning fixes bug that could repeatedly crash nodes
A Core Lightning flaw affected versions v0.12.0 through v26.06.7. Version v26.06.8 completed the fix after an earlier patch missed another crash path.

Core Lightning has fixed LNF-2026–0004, a vulnerability that could repeatedly crash a payment node. The research advisory disclosed on November 13 identifies versions v0.12.0 through v26.06.7 as affected and v26.06.8 as fixing both described variants. This concerns a Lightning implementation, rather than a reported breach of Bitcoin's base protocol.
Details
The flaw involved insufficient checks on payment-channel identifier uniqueness. Conflicting records could violate assumptions inside the software and cause it to terminate. One variant allowed repeated disruption, while another could leave a node in a persistent crash loop after restarting.
The first repair appeared in v26.06.6, published July 22. It addressed the original failure path but did not cover every case involving previously closed channels. A broader fix was included in v26.06.8, published September 22. The release publication dates are confirmed by the project's official repository; detailed disclosure followed later.
Researcher Nishant Bansal's advisory credits the smite testing tool with discovering the issue and Crypt-iQ with identifying an additional variant. The advisory recommends using the latest release: a fix existing in v26.06.8 is not a reason to disregard subsequent security updates.
What it means for markets
Users should distinguish individual Lightning implementations from Bitcoin itself. A vulnerability in a particular node implementation does not establish that every wallet is affected or that every participant lost funds. The advisory does not provide a confirmed aggregate theft amount resulting from this flaw.
Node availability matters for operating payment channels, making repeated outages more than a cosmetic interface issue. Technical exposure should nevertheless be distinguished from demonstrated financial losses. This report concerns fixes that have already shipped and the importance of current software, rather than a new patch released on November 17. Wallet-security fundamentals are covered in the seed-phrase guide, with information about the underlying asset on the Bitcoin page.



Comments