EN
EN Current RU
Telegram
Daily

Bitcoin Optech Podcast Discusses Two Eclair DoS Bugs Fixed in July

A Bitcoin Optech podcast published October 20, 2026, discussed two denial-of-service vulnerabilities in Eclair and said both were fixed in version 0.14.1 in July.

Share
Telegram X Bluesky Reddit WhatsApp
a close up of a rack of computer equipment
Photo by Tyler on Unsplash

Two vulnerabilities, fixed in a past release

A Bitcoin Optech podcast published October 20, 2026, discussed two denial-of-service vulnerabilities in Eclair, a Lightning implementation. The podcast said both bugs were fixed in Eclair 0.14.1 in July. The discussion was a recap of fixes already included in a past release, not an announcement of a new patch.

A rate-limiter race could exhaust memory

According to the Bitcoin Optech podcast, the first bug involved a race between checking for a channel-opening request and adding it to a rate limiter. The speakers said that sending two or more open_channel messages could allow each to pass the limiter.

The podcast said Matt Morehouse measured the resulting memory leak at up to 1 MB per second, potentially continuing until a node crashed. The recap also described the fix as adding the temporary channel ID to the rate limiter atomically and synchronously, rather than asynchronously.

The other bug could persist across restarts

The podcast described a second bug that could leak memory and write actors to disk. It said that after a restart, loading those actors from disk into memory could cause the node to crash immediately, followed by repeated crashes on subsequent restarts.

The podcast did not confirm exploitation

Asked whether either vulnerability had been exploited, Erick Cestari said he did not think so. He added that Eclair operators usually update their own node and patch it promptly. That was his assessment in the podcast, not confirmation that exploitation never occurred.

For operators reviewing their deployments, the reported fixes were in version 0.14.1, which the podcast said was released in July. The October discussion did not identify a newly issued fix or establish whether any particular node remained vulnerable.

Sources

  1. Bitcoin Optech Newsletter #427 Recap Podcast

← All posts