As reported by PANews on November 17, 2026, citing CryptoSlate, Lightning Network developers had fixed an LND vulnerability that could cause a node to misread payment-channel records after a restart. The issue concerned how LND saved and restored channel updates, not a reported loss of funds.
The record format used a 16-bit counter to store the number of entries. At 65,536 entries, the counter could wrap to zero. On restart, a node could then read the record as an empty list, potentially omitting settled hashed timelock contracts (HTLCs) and compromising the channel’s accounting integrity.
Developers said a connected node could drive the entry count toward that limit by repeatedly sending fee updates and commitment signatures while withholding the required revocation messages. That describes a possible way to trigger the bug; the report did not establish that it had been exploited.
LND released v0.21.8-beta and v0.20.8-beta on November 11. According to the report, the fixes add a safeguard when writing records and validate older records when loading them.

