For Lightning Network node operators, the issue was in how LND saved and restored payment-channel updates. As reported by ChainCatcher on November 17, 2026, citing CryptoSlate, developers had fixed a bug that could cause a node to misread a channel record after restarting.
The record used a 16-bit counter to track its entries. At 65,536 entries, the counter could wrap to zero, causing the node to read the record as an empty list. That could omit settled hash time-locked contracts (HTLCs)—conditional payments used by Lightning—and compromise the channel’s accounting integrity.
Developers said a connected node could drive the entry count toward that limit by repeatedly sending transaction-fee updates and commitment signatures while withholding required revocation messages. LND released v0.21.8-beta and v0.2.8-beta on November 11, 2026. The fixes add protection when writing records and validate older records when loading them.
At the time of the report, it had not been confirmed whether anyone had exploited the bug or whether it had caused any loss of funds.
