Fact-check findings
What an automated fact-checker found when it re-read Core Lightning (CLN) against the sources the page cites. Only the most recent review is shown.
These findings are produced by an automated reviewer, and its results vary between runs: the same page, checked three times on the same day, came back with 15%, 20% and 34% of its claims disputed, mostly because each run extracted a different number of claims. Treat what follows as leads, not rulings.
“Disputed” means the reviewer could not reconcile the claim with the evidence it cited. It does not mean the claim is false. “Unverifiable” means no reachable source settled it either way.
Nothing here changes the page on its own. A proposed correction is applied only after a human moderator approves it; until then the page reads as it did when reviewed.
disputed
3 claimsThe reviewer could not reconcile the claim with the evidence it cited. This is a lead, not a ruling that the claim is false.
- #1[disputed][awaiting moderator]in the timeline
“2022-06-01”
reviewerBlockstream rebranded c-lightning to Core Lightning in June 2022The cited Blockstream post dates the rebrand to March 31, 2022, not June 1, 2022.Proposed correction (not yet applied)2022-03-31 - #10[disputed][awaiting moderator]in section: August 2026 AI-Generated CVE Crisis and Emergency Shutdown
“On August 26, 2026, Blockstream issued an emergency advisory directing all CLN node operators to take their nodes offline immediately, citing multiple confirmed critical vulnerabilities.”
reviewerEmergency advisory on August 26 directed all CLN operators to take nodes offline immediatelyA cited page contradicts the characterisation. I did not fetch the TFTC emergency-shutdown article, so the correction rests on two other outlets. Related timeline[5] entry repeats the same framing.Proposed correction (not yet applied)On August 26, 2026, a Bitcoin developer posted an urgent warning urging CLN node operators to shut down; the Core Lightning team responded that operators did not need to shut down and should upgrade promptly or, if unable, restart with the --offline flag. - #11[disputed][awaiting moderator]in the timeline
“Blockstream issues emergency advisory directing all CLN node operators to take nodes offline immediately due to multiple confirmed critical vulnerabilities. No active exploitation or fund losses confirmed at this stage.”
reviewerTimeline entry repeats that Blockstream directed all operators offline on Aug 26Same underlying error as the sections[3] finding.Proposed correction (not yet applied)A Bitcoin developer urges CLN node operators to shut down due to critical vulnerabilities; the Core Lightning team advises upgrading promptly, or restarting with --offline if unable. No active exploitation or fund losses confirmed at this stage.
unverifiable
4 claimsNo source the reviewer could reach confirms or contradicts the claim.
- #2[unverifiable][awaiting moderator]in the timeline
“Blockstream releases c-lightning, the first Lightning Network implementation, led by Rusty Russell.”
reviewerc-lightning was released in August 2015 and was the first Lightning implementationCited source supports neither the August 2015 date nor the 'first implementation' superlative, which is contestable (several implementations were developed in parallel). Not rewritten because no fetched source gives a replacement. - #9[unverifiable][awaiting moderator]in section: Vulnerability Details — v26.06.8 Patch
“No CVE identifiers had been publicly assigned as of the advisory date.”
reviewerNo CVE identifiers had been assignedAbsence of CVEs in coverage is consistent but no source states none were assigned. - #12[unverifiable][awaiting moderator]in the timeline
“Bitcoin Red Team begins submitting AI-generated CVE reports against Core Lightning repositories using the Kimi K3 model, generating ~4,962 findings across 390+ Bitcoin repositories.”
reviewerAI-generated CVE reports began around August 14 using Kimi K3, with 4,962 findings across 390+ repositories in ~27.5 hoursThe cited source does not contain the specific model, counts or date (it says ~Aug 13). Other cited sources (Cyber Kendra, TFTC AI CVE article) were not fetched. - #18[unverifiable][awaiting moderator]in section: Project Overview
“CLN occupies a smaller portion of the network but is considered a reference implementation for BOLT specification compliance.”
reviewerCLN is smaller than LND and considered a reference implementation for BOLT complianceNot checked against a fetched source; 'considered a reference implementation' is vague and unattributed.citedcorelightning.org/
stale
2 claimsThe claim was accurate when written but events since have overtaken it.
- #15[stale][awaiting moderator]in the summary
“A patch (v26.06.8) has been available since September 22, 2026, but uptake remains incomplete across the operator base.”
reviewerA patch has been available since September 22 but uptake remains incomplete; v26.06.8 is the fixv26.06.8 is no longer the latest fix, and the 'uptake incomplete' assertion has no source.Proposed correction (not yet applied)A patch (v26.06.8) became available on September 22, 2026, and v26.06.9, released October 7, 2026, followed it with further security fixes. - #16[stale][awaiting moderator]in section: Operator Exposure and Recommended Actions
“(1) upgrade to v26.06.8 immediately from the official GitHub release page”
reviewerOperators should upgrade to v26.06.8 immediatelyAdvice was accurate on Oct 2 but is superseded.Proposed correction (not yet applied)(1) upgrade to the latest release (v26.06.9 as of October 7, 2026) immediately from the official GitHub release page
partially supported
4 claimsThe cited evidence supports part of the claim but not all of it.
- #3[partially supported][awaiting moderator]in section: Project Overview
“it was first released in August 2015 and has been running on Bitcoin mainnet since early 2018”
reviewerc-lightning has been on Bitcoin mainnet since early 20182018 mainnet portion is supported; the August 2015 first-release date is not in the cited source. - #4[partially supported][awaiting moderator]in section: Active Exploitation Warning — October 2026
“On October 2, 2026, Blockstream issued an urgent security advisory confirming that attackers are actively targeting CLN nodes running version 26.06.7 or earlier.”
reviewerBlockstream issued the urgent advisory on October 2, 2026Sources conflict on Oct 1 vs Oct 2; the substance (active targeting of 26.06.7 and earlier) is confirmed. Attribution to Blockstream vs the Core Lightning team is loose. - #5[partially supported][awaiting moderator]in section: Active Exploitation Warning — October 2026
“Blockstream recommended that operators unable to upgrade immediately restart their nodes in offline mode as a temporary mitigation.”
reviewerBlockstream advised operators unable to upgrade to restart in offline mode as a mitigation (October advisory)The --offline guidance is documented for August; I could not confirm it was reissued in the October advisory. - #8[partially supported][awaiting moderator]in section: Vulnerability Details — v26.06.8 Patch
“Third, and most critically, a channel-closing bug causes a node to misidentify a revoked commitment transaction as a legitimate cooperative close, causing the node to miss the penalty transaction window.”
reviewerChannel-closing bug makes a node misidentify a revoked commitment as a cooperative closeMechanism comes from a single outlet's hedged description, not the cited sources, and is stated more definitively on the page. Also note the page's cited sources describe the user as the one who could suffer a penalty.
confirmed
5 claimsThe cited evidence supports the claim as written.
- #6[confirmed][no action needed]in section: Active Exploitation Warning — October 2026
“The team withheld certain test suites from the public repository to prevent attackers from reverse-engineering the exact attack surface while operators complete upgrades.”
reviewerTest suites were withheld from the public repositorySupported by news and GitHub release notes. - #7[confirmed][no action needed]in section: Vulnerability Details — v26.06.8 Patch
“Version 26.06.8, released on September 22, 2026, closes three confirmed bug classes identified through responsible disclosure.”
reviewerv26.06.8 was released September 22, 2026 and closes three bug classes (crash-on-send, REST memory exhaustion, channel-closing bug)Date and bug classes confirmed. One outlet gave Sept 24, but GitHub says Sept 22. - #13[confirmed][no action needed]in the timeline
“Core Lightning v26.06.7 released, addressing the vulnerabilities identified through the August AI-generated CVE campaign.”
reviewerv26.06.7 released August 28, 2026Date confirmed by GitHub and crypto.news. - #14[confirmed][no action needed]in the timeline
“Core Lightning team investigates new issues potentially affecting experimental features and operator funds.”
reviewerSept 16: team investigating new issues potentially affecting experimental features and fundsSupported. - #17[confirmed][no action needed]in section: Fund Losses and Exploitation Confirmation Status
“As of October 2, 2026, Blockstream had not publicly confirmed that any operator funds were successfully stolen as a result of the active exploitation campaign.”
reviewerAs of the advisory, no funds were publicly confirmed stolenConfirmed as of Oct 2. Page offers no later status; see omissions.