WORLDTECH NEWS Global technology intelligence.Contact
Bitcoin & Crypto SINGLE SOURCE

Core Lightning needed two patches to close a node-crash flaw

A visual representation of bitcoin mining with smartphone and blockchain concept using Scrabble pieces.
Illustrative photo.Photo by Leeloo The First on Pexels

Developers of Core Lightning, a software implementation used to run nodes on Bitcoin's Lightning Network, needed two security patches to shut a flaw that could repeatedly crash payment nodes. According to CryptoSlate, the first fix left a second attack path open that could keep affected nodes offline even after they restarted.

How the duplicate-identifier flaw arose

The flaw, tracked as LNF-2026-0004, lies in the step where payment channels are opened. Each channel receives an identifier derived from the Bitcoin transaction output that funds it. Core Lightning could accept several channels pointing at the same funding output, which generated identical identifiers that conflicted with the software's internal assumptions.

Security researcher Nishant Bansal found that attackers could exploit this to crash nodes. In the first variant, no Bitcoin transaction fees were needed, since the fraudulent channels never required on-chain funding.

Why the July patch fell short

Developers addressed the original problem in version 26.06.6, released on July 22, after researchers had privately reported the reconnection attack earlier that month. The update stopped new channels from reusing funding outputs tied to live channels, and changed connection handling so that duplicate records already stored no longer triggered the crash.

The protection did not reach identifiers linked to closed channels, and researcher Crypt-iQ independently identified this remaining weakness. Unlike the first attack, this closed-channel variant carried on-chain fees, yet it could leave a node unable to recover without a software upgrade.

What the September update changed

Version 26.06.8, released in September, widened duplicate-identifier checks to cover active and closed channels belonging to different peers. It also allowed nodes holding previously stored duplicate records to recover without crashing repeatedly.

According to the disclosure, closed-channel collisions could still cause a persistent restart loop before the second patch, and a separate free, nonpersistent path to the same assertion also existed.

Exposure for operators on older software

The second patch closed the remaining attack route, but node operators running outdated versions remain exposed. The facts do not say how many nodes run those versions, nor whether any attacks took place or funds were lost.

Open questions

  • How many nodes still run versions prior to 26.06.8?
  • Were these flaws exploited in practice before the patches were released?

Key facts

  • A November disclosure showed that a July repair left a persistent crash route open.
  • Core Lightning's first security patch, released in July, blocked one crash method but missed a persistent vulnerability.
  • A second patch in September closed the remaining attack route, but operators running outdated software stay exposed.
  • The vulnerability is tracked as LNF-2026-0004 and stems from duplicate payment-channel identifiers.
  • Security researcher Nishant Bansal discovered the flaw, which affects Core Lightning.

Sources & evidence