Core Lightning (CLN) is a Lightning Network node implementation, and it has had a rough autumn. In mid-August, according to Crypto Briefing, the project received a high volume of AI-generated vulnerability reports over about ten days. On August 28 it shipped 26.06.7 as an emergency security release, as binaries only, with the source withheld for 14 days. Maintainers said at the time that no vulnerability was known to be actively exploited.
The quiet didn’t last. On September 16 the project said it was investigating a possible issue in experimental features that could affect funds. Version 26.06.8 followed on September 22. Then on October 2 the project told operators on 26.06.7 or earlier to upgrade as soon as possible, amid reports that attackers were targeting unpatched nodes (Cointelegraph).
The project urged operators on 26.06.7 or earlier to upgrade as soon as possible, amid reports that attackers were targeting unpatched nodes.
What was fixed, and why the source was held back
The 26.06.7 announcement didn’t describe the bugs. Withholding the source for 14 days gave attackers less to work with while operators upgraded. Bitcoin Optech says reproducible builds let users confirm the binaries match the source once it is published.
Cointelegraph lists these fixes in 26.06.8: flaws that could crash sender nodes, requests that could exhaust memory in the REST interface, and a channel-closing bug that could cause users to lose funds to a penalty. The release credits the Bitcoin Red Team, 12 other named individuals or groups, and anonymous reporters.
The –offline stopgap
Bitcoin Optech reports that operators who wanted to wait for the source before upgrading could restart with the –offline flag. The node then stops making or accepting peer connections but keeps enforcing on-chain rules against cheating peers. That was a temporary measure offered at the time of 26.06.7, while the source was embargoed. Given the later warning, upgrading is the better path now.
Who Benefits and How
The people who benefit directly are Lightning node operators, who should be on at least 26.06.8 and ideally the newest release. Everyone else gains indirectly: fewer crashed or drained nodes means a more dependable network for the payments that route through it. The fixes are released now, so the benefit is available to any operator who upgrades.
What we still don’t know
- Which specific bugs attackers are using is unknown. Cointelegraph says its article does not state the attack method or impact.
- “Attackers are targeting unpatched nodes” comes from reports Cointelegraph cites. No losses are confirmed.
- No formal CVEs had been published by late August, per Crypto Briefing.
- The number of AI-generated reports was not given. The sources say only “a high volume.”
- Details here rely on news coverage and Bitcoin Optech rather than the project’s own release notes for either version.
Quick answers
Which version should I run, and were funds lost?
Run at least 26.06.8, and the newest release available. No confirmed loss reports turned up, but the channel-closing bug fixed in 26.06.8 could cause fund loss to a penalty, so patching still matters.
Do other Lightning implementations have the same bugs?
These reports concern Core Lightning. Other implementations have separate code and their own releases.
Sources
- Bitcoin Optech: Newsletter, August 28, 2026 (Aug 28, 2026)
- Crypto Briefing: Core Lightning patches vulnerabilities in version 26.06.7 amid AI report surge (Aug 28, 2026)
- Cointelegraph: Core Lightning urges upgrade amid reports attackers targeting unpatched nodes (Oct 2026)
