EN
EN Current RU
Telegram
Daily

Core Lightning flaw could crash nodes repeatedly until stored message was removed

Bitcoin Optech reported that a malformed channel announcement could crash Core Lightning nodes running versions 25.02 through 26.04—and persist as a restart problem until manually removed.

Share
Telegram X Bluesky Reddit WhatsApp
Server rack with blinking green lights
Photo by Domaintechnik on Unsplash

A malformed announcement passed validation

Bitcoin Optech’s Oct. 30, 2026 newsletter reported a denial-of-service vulnerability affecting Core Lightning (CLN) versions 25.02 through 26.04, disclosed by Nishant Bansal on Delving Bitcoin. The report described a channel announcement that named the same node at both ends.

According to Bitcoin Optech, CLN did not check that the two node IDs in an announcement were different. As a result, the malformed message could pass validation and be written to the on-disk gossip store before CLN loaded it into the in-memory channel graph.

Why the crash could return after a restart

Bitcoin Optech said that loading the announcement added the unknown node twice. That triggered a no-duplicates assertion in gossipd and crashed the node.

The newsletter also reported that the stored message could crash the node again on every restart. Upgrading alone did not remove that message; the operator had to remove it manually.

The operational caveat

Bitcoin Optech advised operators still using an affected version to upgrade to the latest release. Its report’s key caveat is that an upgrade by itself would not clear an already stored malformed announcement, which could continue to cause crashes until removed.

The disclosure was reported in the Oct. 30, 2026 newsletter, so this is a report of a previously disclosed issue, not a claim that the vulnerability is newly discovered.

Sources

  1. Bitcoin Optech Newsletter #429

← All posts