Skip to content
Market MoodExtreme Fear11
Market Cap: $2.22T −2.43%24h Vol: $76.75BBTC: $64,689 +0.12%
NewsMarketsBitcoinEthereumAltcoinsAsiaWeb3EventsAbout Us
LanguageENRU
Subscribe Pro
Bitcoin

Lightning Network Developers Issue Two Patches to Fix Channel‑Crash and Payment‑Loss Bugs

Bitcoin Lightning’s LND and Core Lightning teams released updates to stop a counter‑overflow flaw that could erase settled payments and a duplicate‑outpoint bug that could crash nodes.

· 2 min read
gold and black round emblem
Photo by Kanchanara on Unsplash

Key takeaways

  • LND’s counter bug reset after 65,536 entries, risking lost payment records
  • Core Lightning’s duplicate outpoint flaw could crash nodes repeatedly
  • Both projects released patches in November 2026 to mitigate the risks

Bitcoin’s Lightning Network, the layer‑two protocol that enables instant, off‑chain payments, faced two separate software vulnerabilities in November 2026. The first, discovered in the popular LND implementation, involved a 16‑bit counter that could overflow after 65,536 payment‑update entries, potentially causing a node to forget settled payments once it restarted. The second flaw, affecting Core Lightning, allowed an attacker to reuse a channel’s funding outpoint and trigger a crash loop that prevented a node from monitoring other channels. Both bugs threatened the integrity of channel accounting and the reliability of node operations, prompting rapid responses from the developers.

BitcoinBTC · 24h
$64,689+0.12%

LND Counter Overflow Patch

According to CryptoSlate, LND maintainer Olaoluwa Osuntokun—known as Roasbeef—identified the issue in early November. The software stored the number of pending acknowledgements in a 16‑bit unsigned integer, which caps at 65,535. When the list grew to 65,536 entries, the counter reset to zero while the updates were still written to disk. On restart, the node could misinterpret the zero as an empty list and drop a previously settled hashed‑timelock contract (HTLC), erasing the record of a completed payment. The patch, released as v0.21.8‑beta and v0.20.8‑beta on November 11, added checks to block oversized update lists and improved the recovery logic for older data. No confirmed exploitation or financial loss was reported, but the fix was considered essential to maintain channel consistency.

Core Lightning Duplicate‑Outpoint Fix

Tokenpost reported that Core Lightning’s vulnerability, first described by researcher Nishant Bansal on November 13, could let an attacker create duplicate pending channels by reusing a funding outpoint. The attack could crash a node when it reconnected, and the crash would persist across restarts. A second attack route involved closing a channel with the same outpoint as a previously closed channel, which also triggered a crash loop. The Core Lightning team released v26.06.6 on July 22 to block outpoint reuse among live channels and adjust reconnect handling. A subsequent release, v26.06.8 on September 22, extended the checks to closed channels and allowed nodes to load and close duplicate records. Bansal urged operators to upgrade to the latest release, noting that the disclosure did not quantify affected nodes or losses.

Implications for Node Operators

Both bugs highlighted how subtle implementation details can undermine the Lightning Network’s reliability. Operators running LND or Core Lightning should ensure they are on the latest stable releases—LND v0.21.8‑beta or newer, and Core Lightning v26.06.8 or newer—to avoid the counter‑overflow and crash‑loop scenarios. While no financial damage has been confirmed, the potential for lost settlement records or prolonged downtime could impact merchants and users relying on instant payments. The patches also demonstrate the community’s rapid response to security findings, a critical factor for the network’s ongoing adoption.

What to Watch Next

The Lightning Network’s security team will likely continue to audit state‑transition logic, especially around counter management and channel identifiers. Developers may release further updates to harden the protocol against similar overflow or duplication attacks. Node operators should monitor the official repositories for any new advisories and test patches in staging environments before deploying to production.

Sources

  • Tokenpost: Core Lightning Needed Two Releases to Close a Channel Crash Flaw
  • CryptoSlate: Bitcoin Lightning developers needed two patches to stop a potentially costly attack

Not financial advice. Crypto assets are volatile and you can lose money. Read our Financial Risk Disclosure.

Lightning NetworkLNDCore LightningHTLCNode securitySecurity
Newsletter

Get the BitcoinEast Daily

Top crypto news, analysis, and market insights, delivered every day.