For anyone relying on a Lightning node to keep accurate payment-channel records, the concern was what LND might read back after a restart. In a report published on November 17, 2026, ChainCatcher, citing CryptoSlate, said developers had fixed a bug that could cause LND to miss settled hashed timelock contracts (HTLCs) when restoring channel updates. That could compromise a channel’s accounting integrity.
The problem involved a 16-bit counter used to record the number of entries. At 65,536 entries, it could overflow to zero, causing a restarting node to interpret the saved records as an empty list. Developers said a connected node could drive the entry count upward by repeatedly sending transaction-fee updates and commitment signatures while withholding the required revocation messages.
LND released v0.21.8-beta and v0.2.8-beta on November 11, adding a safeguard when writing records and checks when loading older ones. At the time of the November 17 report, there was no confirmation that the bug had been exploited or had caused any loss of funds.
