
Bitcoin’s Core Lightning software program required two safety patches to remove a vulnerability that would repeatedly crash cost nodes and doubtlessly expose funds held in different channels.
A Nov. 13 safety disclosure revealed that an preliminary restore launched in July failed to deal with a second assault technique that would hold affected nodes offline even after they restarted.
The vulnerability, tracked as LNF-2026-0004, affected Core Lightning, one of many software program implementations used to function nodes on Bitcoin’s Lightning Community.
Safety researcher Nishant Bansal found that attackers might exploit how Core Lightning assigned identifiers to cost channels, creating duplicate data that brought on the software program to crash.
The weak point originated within the community’s channel-opening course of, the place every cost channel receives an identifier derived from the Bitcoin transaction output that funds it. Core Lightning might settle for a number of channels referencing the identical funding output, producing similar identifiers that conflicted with assumptions in its inside software program.
Within the first assault, a malicious peer might create duplicate pending channels and crash a sufferer’s node just by reconnecting. The assault required no Bitcoin transaction charges as a result of the fraudulent channels didn’t want on-chain funding. Every subsequent reconnection might set off one other crash, permitting attackers to repeatedly interrupt cost processing.
Nevertheless, researchers recognized a extra persistent variation involving beforehand closed channels.
By reusing an identifier related to a closed channel and subsequently closing one other channel with the identical identifier, attackers might set off a software program failure that continued throughout restarts.
In contrast to the preliminary assault, this technique required on-chain transaction charges however might depart the node unable to get well with out a software program improve.
Why Core Lightning’s first safety patch failed
Core Lightning builders addressed the unique vulnerability in model 26.06.6, launched on July 22, after researchers privately reported the reconnection assault earlier that month.
The replace prevented new channels from reusing funding outputs related to current stay channels. It additionally modified connection dealing with to stop duplicate data already saved from triggering the unique crash.
Nevertheless, the safety didn’t prolong to identifiers related to closed channels, leaving the second assault route accessible.
Researcher Crypt-iQ independently recognized the remaining weak point, prompting builders to introduce broader safeguards in model 26.06.8, launched Sept. 22.
The second replace expanded duplicate-identifier checks throughout energetic and closed channels belonging to completely different friends. It additionally allowed nodes containing beforehand saved duplicate data to get well with out repeatedly crashing.
Discover the 2 repairs
The primary repair blocked outpoints reused amongst that peer’s stay channels and dealt with reconnect duplicates. Closed-channel collisions might nonetheless trigger a persistent restart loop.
The broader repair rejected IDs utilized by stay or closed channels throughout all friends and let nodes load and shut duplicates already saved.
Operators ought to improve to the newest launch to stop collisions and deal with saved duplicates.
The closed-channel loop proven is the documented persistent path; a separate free nonpersistent path additionally existed. This qualitative schematic doesn’t present exploitation, losses or affected-node counts.
The potential monetary penalties prolonged past disrupted Lightning funds.
In keeping with the advisory, nodes pressured offline might lose the power to watch Bitcoin’s blockchain for makes an attempt to settle channels utilizing revoked transaction states.
That would permit dishonest counterparties to say funds utilizing outdated channel balances. Offline nodes might additionally miss deadlines for gathering time-sensitive funds, putting Bitcoin held in unrelated channels in danger.
The researchers didn’t report confirmed exploitation or monetary losses.
The findings have an effect on Core Lightning variations previous the whole September restore, with the reconnection vulnerability relationship again to model 0.12.0 and the persistent closed-channel crash launched in model 25.05.
Builders have since launched further safety updates, together with model 26.06.10, which addresses different vulnerabilities involving channel operations, cost decision, and distant crashes.
Core Lightning’s maintainers have urged operators to improve to the newest launch to guard their nodes towards the disclosed weaknesses.