Core Lightning developers needed two security patches to eliminate a vulnerability that could repeatedly crash payment nodes and potentially put funds in other channels at risk. A November 13 security disclosure revealed that the first repair, released in July, left a second attack method available. The second method could prevent affected nodes from recovering even after restarts. Operators using outdated software remain exposed despite the September repair.
The vulnerability, designated LNF-2026-0004, affected Core Lightning, an implementation used to run nodes on Bitcoin's Lightning Network. Security researcher Nishant Bansal found that attackers could cause crashes by exploiting the way Core Lightning assigned payment-channel identifiers. Each identifier comes from the Bitcoin transaction output funding the channel. Core Lightning could accept several channels referencing one funding output, creating duplicate identifiers that violated internal software assumptions.
A malicious peer could establish duplicate pending channels and then crash the target node by reconnecting. The method incurred no Bitcoin transaction fees because the fraudulent channels required no on-chain funding. Repeated reconnections could cause repeated crashes and interrupt payment processing. However, researchers found a second method that produced a more persistent failure through closed channels. An attacker could reuse a closed channel's identifier and then close another channel carrying that identifier, causing a failure that survived restarts. This method required on-chain transaction fees and could prevent recovery until a software upgrade.
Core Lightning developers released version 26.06.6 on July 22 after researchers privately disclosed the reconnection attack earlier that month. The update blocked new channels from referencing funding outputs already used by live channels. Changes to connection handling also stopped duplicate records already in storage from causing the original crash. However, the update left identifiers from closed channels unprotected. Researcher Crypt-iQ independently found the remaining weakness, prompting developers to release broader protections in version 26.06.8 on September 22. That update checked for duplicate identifiers among active and closed channels associated with different peers. The update also enabled recovery for nodes with previously stored duplicate records without recurring crashes.
The advisory warned that nodes forced offline could become unable to check Bitcoin's blockchain for channel settlements involving revoked transaction states. Dishonest counterparties could consequently claim funds through outdated channel balances. Offline nodes could also miss deadlines to collect time-sensitive payments, putting Bitcoin in unrelated channels at risk. Researchers reported no confirmed exploitation or financial losses.
The findings concern Core Lightning versions released before the complete September repair. The reconnection vulnerability dates to version 0.12.0. The persistent crash involving closed channels first appeared in version 25.05. Developers subsequently issued further security updates, including version 26.06.10, addressing other weaknesses involving channel operations, payment resolution and remote crashes. Core Lightning's maintainers urged operators to install the latest release to protect nodes from the disclosed vulnerabilities.
Core Lightning Patches Vulnerability That Could Crash Nodes and Risk Funds
CryptoSlateShare
Core Lightning released two security updates to fix a vulnerability news that could crash nodes and risk funds. The flaw, LNF-2026-0004, let attackers exploit payment-channel IDs, causing repeated failures. A July patch stopped one method, but a broader fix came on September 22. Affected nodes might miss blockchain updates, risking Bitcoin in other channels. No confirmed losses were reported. Market crash news remains unlikely, but node operators are urged to update.
Source:Show original
Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information.
Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.