A Lightning payment channel depends on its saved updates to reconstruct its state after a node restarts. As reported on November 17, 2026, LND developers had fixed a bug that could cause a node to misread those records and omit settled hashed timelock contracts (HTLCs) from its channel accounting.
The problem was a 16-bit counter used to record the number of entries when saving and restoring channel updates. At 65,536 entries, the counter could overflow to zero. After a restart, the node could then interpret the record as an empty list, potentially compromising the integrity of its payment-channel accounting. This was a risk described in the report, not a confirmed loss of payment records.
According to the developers, a connected peer 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.20.8-beta on November 11, 2026. The versions add a write guard and validate older records when loading them.