- Home
- Blockchain Technology
- Core Lightning Tells Node Operators to Upgrade Now as Attackers Target Older Versions
Core Lightning Tells Node Operators to Upgrade Now as Attackers Target Older Versions

Core Lightning has issued an urgent warning to Bitcoin Lightning Network node operators: attackers are actively targeting systems still running version 26.06.7 or earlier, and anyone affected needs to upgrade immediately. The team behind the popular open source Lightning node implementation says it has received reports of attacks against unpatched nodes, though it has not disclosed which vulnerabilities are being exploited or whether any funds have been lost so far.
By Amir Hassan | October 3, 2026
Table of Contents
The Alert
"Urgent security update: If you're running version 26.06.7 or earlier, please upgrade to the latest release as soon as possible," the Core Lightning team said in its warning to operators.
The message is deliberately short on detail. Core Lightning has not said which vulnerabilities the reported attacks involve, what an attacker could achieve against an unpatched node, or whether the activity is connected to the flaws fixed in recent releases. That ambiguity is part of responsible disclosure: saying too much before operators have patched would hand attackers a roadmap.
For regular investors, the practical takeaway is simple. If you run a Lightning node — or know someone who does — the fix is already available, and the window to apply it without incident is now.
What the September Patch Actually Fixed
The latest stable release, version 26.06.8, shipped on September 22 with bug fixes and patches covering vulnerabilities that had been responsibly disclosed to the project. The release notes credited the Bitcoin Red Team alongside 12 named researchers and groups, plus reporters who chose to stay anonymous. Core Lightning strongly recommended installing the release and said there was no embargo period, though developers temporarily withheld a small number of tests from the public release to make it harder for prospective attackers to reverse engineer the underlying flaws while operators were still updating.
Several of the fixes can be identified from the changelog, and each carries a different kind of risk:
- Node crash bug — a problem capable of crashing a sender's node, disrupting payment routing.
- Memory exhaustion — requests through Core Lightning's REST interface that could consume available memory and degrade or disable a node.
- Channel closing flaw — under certain conditions, a bug that could result in a user losing funds to a penalty when a channel was closed, a direct financial risk rather than a mere availability issue.
Core Lightning has not confirmed that any of those specific flaws are what attackers are now targeting. The warning only states that reports have been received of attacks against unpatched nodes.
A Summer of Security Work
The current alert is the latest chapter in a busy few months for the project. In August, Core Lightning confirmed multiple vulnerabilities after reviewing a large volume of AI-generated Common Vulnerabilities and Exposures reports. Not every submission represented a genuine problem — developers had to validate the wave of reports before deciding which issues warranted fixes — but several were confirmed as legitimate.
Version 26.06.7, released on August 28, addressed vulnerabilities identified during that effort. In an unusual step, developers withheld the source code for two weeks to give operators time to update before attackers could study the changes and work backwards to identify the patched flaws. The source was published after the embargo ended in September.
Security work continued into September. On September 16, the team said it was investigating reports of a potential problem involving experimental features that could affect user funds, though details were not immediately released. Version 26.06.8 followed six days later.
What Operators Should Do
Upgrading is the project's main recommendation, and it always has been. During the earlier response, Core Lightning told operators that nodes unable to install the security release immediately could temporarily run in offline mode instead of stopping the daemon entirely. That configuration disconnects a node from Lightning peers and stops payments from being sent, received or routed, while allowing the daemon to keep watching the Bitcoin blockchain for channel-related transactions — something a fully stopped node would not do.
The distinction matters. A routing node earns fees by forwarding payments, so downtime has a cost. Offline mode preserves the node's ability to monitor its channels and respond to force-close situations on-chain while cutting off the attack surface that peer connections create. It is a stopgap, not a solution, but it is far better than an unpatched node exposed to the public network.
Why This Matters Beyond Node Runners
The Lightning Network is Bitcoin's payments layer, and routing nodes are its plumbing. Most casual Bitcoin users never run one, but exchanges, wallets and payment processors increasingly rely on Lightning channels for fast, cheap transfers. A wave of compromised routing nodes would not threaten Bitcoin's base layer, but it could freeze or steal channel funds and erode confidence in Lightning-based services.
The episode also highlights a newer dynamic: the August disclosure round was triggered partly by AI models being used to comb open source code for vulnerabilities. That cuts both ways. The same tooling that helps researchers find bugs quickly also lowers the barrier for attackers probing live systems, which compresses the time between a patch's release and its exploitation in the wild. Core Lightning's decision to embargo source code — twice in two months — reflects exactly that pressure.
For now, the project's guidance stands: check your version, and if it is 26.06.7 or older, upgrade today. Attackers are not waiting, and neither should operators.
The cryptocurrency market remains highly volatile. This article is for informational purposes only and does not constitute financial advice.
Disclaimer: This article is for informational purposes only and does not constitute financial advice.
27 Comments