Core Lightning Ships 26.06.7 as AI-Assisted Reports Spur Emergency Upgrade
Editorial Team
••📖5 min read
Core Lightning released version 26.06.7 after maintainers triaged a burst of vulnerability reports, some described by independent accounts as AI-generated. The project is withholding technical details for two weeks and says operators who cannot upgrade should isolate the node with --offline rather than switch off the machine, because an offline daemon can still watch Bitcoin for fraudulent channel closes.
Core Lightning released signed version 26.06.7 on Aug. 28 after maintainers triaged a surge of vulnerability reports.
Independent accounts say several reports in the roughly 10-day burst were generated with AI; the project itself confirms only that AI is increasing report volume and pace.
Operators who cannot upgrade immediately are told to restart with --offline, not power down, so the daemon can keep monitoring Bitcoin.
The flaws’ number, severity, exploitability and exploitation status remain undisclosed during a two-week embargo.
The ElementsProject release identifies version 26.06.7, “Quantum-Resistant Lightning Channel VII,” as a point release containing fixes for vulnerabilities responsibly reported by multiple sources. Its maintainers say increasingly capable AI models are raising both the volume and pace of reports. They are withholding the source code and full vulnerability details for 14 days to reduce the chance that attackers reverse-engineer the fixes before nodes update.
The release is usable now as signed binaries. Operators are told to verify the signed checksum manifests and to install the platform tarballs rather than wait for Docker images, which were not yet available at publication. No database migration is required beyond automatic startup changes. The repository lists reports from individual researchers, the Bitcoin Red Team and an address at coinos.io, but does not assign a finding to a particular model or disclose how many reports were accepted.
Charta Health is expanding its insurer tools with a $55 million Series B. Its promise of billing accuracy across payers and providers faces a harder test: showing that better coding reduces disputes rather than simply changes payments.
One account describes roughly 10 days of CVE-style submissions beginning around Aug. 13 and says the small core team validated several as genuine security concerns. A separate report likewise says several AI-generated reports proved real. Those descriptions explain the emergency timing, but they are not a public vulnerability inventory: the project has not said how many issues are fixed, what an attacker could do or whether any flaw has been exploited.
Version 26.06.7 follows 26.06.6, released July 22, according to the same secondary account. It also says versions 26.04 and earlier are unsupported. That branch information is not in the release note itself, so operators should confirm their upgrade path rather than assume an older installation will receive the fixes.
Why shutting down can expose channel funds
The project’s documentation says the implementation has been in production on Bitcoin mainnet since early 2018. Lightning participants lock bitcoin into channels and update balances off-chain, settling the final state on Bitcoin. The node’s continuing role is to watch the blockchain for a counterparty attempting to close with a revoked, outdated balance.
The emergency instruction therefore distinguishes isolation from shutdown. As the operator guidance reported, restarting with --offline cuts connections to other Lightning peers and stops payments from being sent, received or routed, while leaving the software running to monitor Bitcoin. A machine that is powered off cannot see a fraudulent close or respond on-chain.
The project’s watchtower documentation states that the protocol assumes a node stays online and synchronized. A watchtower can monitor for a breach and relay a penalty transaction for an offline node, but it is a separate service; the documentation does not make it a replacement for the emergency upgrade.
More scrutiny, not yet a measured risk increase
The current release is part of a busy month for Bitcoin infrastructure, but the surrounding numbers describe different events. In early August, a separate BTCPay Server flaw exposed credentials for some Lightning nodes and attackers drained funds before a fix, according to the reporting. In late July, the Bitcoin Red Team said it used AI models to scan 390 Bitcoin repositories and produced nearly 5,000 findings, including 85 it rated critical, in about 27 hours. Neither result measures the prevalence or severity of the Core Lightning issues.
Earlier in 2026, Core Lightning patched distinct denial-of-service vulnerabilities in versions 26.04 and 26.06rc2, the secondary account reported. More findings can mean more exposure—or simply more examination. Until the embargo ends, there is no public basis for saying this implementation became less secure, only that the maintainers’ verification and disclosure workload accelerated.
What operators and researchers need next
The regularly scheduled Core Lightning 26.09 release remains planned for late September, but 26.06.7 is the immediate decision point. Operators must either install and verify the signed binaries or, temporarily, run an unupgraded node with --offline while keeping the machine on. Powering down removes the monitoring function the emergency advice is designed to preserve.
When the two-week embargo expires, the source, vulnerability classes and severity should show whether the precaution matched a channel-fund risk, a denial-of-service risk or something else. That disclosure—and evidence of affected versions or exploitation—will determine whether this episode was primarily a successful use of AI in defensive review or a transfer of triage costs onto a small open-source maintenance team.
Operand has raised $31 million across seed and Series A funding for AI due diligence software aimed at private equity firms. Its pitch is to reconstruct businesses from public records and internet traces, but evidence of accuracy and deal-level economics remains limited.
Caitlin Kalinowski resigned over the deliberation and oversight behind OpenAI’s Pentagon agreement. The company says its safeguards prohibit domestic surveillance and autonomous weapons, leaving a dispute over how those limits were established and will be enforced.
The startup formerly known as QuilrAI pairs enterprise AI agents with Guardian agents and charges by agents under management. Its expansion pitch faces established alternatives and unanswered questions about security performance and cost.
Luminal’s Standard Capital-led Series A backs software for running AI models more efficiently on existing GPUs and alternative chips. Its reported processing volume leaves revenue and comparable customer savings unresolved.
Officials project at least US$40 billion in investment from a proposed Philippine technology hub. Its initial land offer leaves later rent and facility costs open, while water supply, ancestral claims and access to jobs remain contested.
Tesla is inviting selected customers to buy its two-seat Cybercab, with December deliveries estimated. A mandatory autonomy subscription and service-area limits make the purchase price only part of the ownership proposition.
The local AI inference project and its ggml engine now promise major-version bumps for incompatible library changes. The release also shows why clearer labels cannot eliminate the cost of keeping downstream apps current.
A 73–25 procedural vote moved a broad energy-permitting deal forward. Its data-center transmission charges could shift costs from other customers, but utility oversight, tribal rights and clean-energy protections remain disputed. Another Senate test is scheduled for November 16.
Commerce Secretary Howard Lutnick faces questions over delayed restrictions on suspected Nvidia chip diversions and the company’s access to rulemaking. Commerce disputes claims of chilled enforcement, while China’s trade leverage complicates the account.
Fermi has signed preliminary agreements for 600MW of powered land with a customer identified in reporting as Amazon. Customer funding and a lighter construction burden offer a route forward, but the developer has lost its TensorWave lease and faces land and financing deadlines.
Meta reports more than 2 million weekly Business Agent businesses, but leaves paid demand undisclosed. Its AI financing has also grown beyond the initial $35 billion offering plan.
Google says its Teamwork framework produced seven mathematical results with Gemini 3.1 Pro, three reproduced with Gemini 3.7 Flash. Human-checked proofs and a formal verification support the research claim, but novelty varies and the cost of reproducing it in the paid preview remains unresolved.
tvOS 27.2.1 brings Siri AI to second-generation and newer Apple TV 4K boxes, according to updated reporting. Eligible owners can keep their existing streamer, but need a nearby paired device with Siri AI enabled.
OpenAI is rolling out ChatGPT Wallet to eligible US Pro subscribers, giving its dots agents tokenized card payments for existing website checkouts. Users approve purchases with biometrics, while merchant acceptance, reliability and demand remain tests for the limited launch.
ASUS is testing its first humanoid robot at an electronics factory, targeting customer pilots in 2027. Its manufacturing experience supplies real tasks and training data, but sustained reliability and commercial economics remain unproven.
Cerebras expects Microsoft cloud-inference revenue to begin in early 2027, subject to service milestones. Quarterly revenue rose 55%, but OpenAI delivery delays, preferential customer terms and long-term infrastructure commitments complicate the expansion.
Meta has expanded Muse’s phone-calling feature beyond early testers to paid US subscribers. The rollout puts routine errands behind a subscription, while business acceptance and an earlier human-contractor experiment complicate the promise of autonomous calls.
Anthropic deployed a fix for authentication problems affecting Claude services and closed the incident on November 13. Later reporting described residual failures, whose connection to the login incident remains unconfirmed.
Treasury Secretary Scott Bessent said agencies had backed export restrictions on Nvidia customer Megaspeed for months. He challenged Commerce’s handling of the case and Nvidia’s safeguards, while Megaspeed denies illicit chip exports to China.