LNbits Ships Urgent 1.7.0 Security Update After November 8 Attacks on Lightning Wallet Servers
LNbits, the open-source Lightning Network wallet and accounts system, released version 1.7.0 on November 10, 2026 and told all operators to upgrade before running their servers, saying every earlier version is affected by a vulnerability found on November 8 and that funds on those versions are at risk of theft.

Table of Contents
LNbits, an open-source wallet and accounts system for the Bitcoin Lightning Network, released version 1.7.0 on November 10, 2026 as an urgent security update. The project said all operators must upgrade before running LNbits again, because every version before 1.7.0 is affected by a vulnerability discovered on November 8 and funds running on those versions are at risk of being stolen.
From shutdown warning to patch
The release follows a wave of attacks that began over the weekend. On November 8, the project's official X account told all users to stop their LNbits servers immediately while security patches were prepared, according to Bitcoin Magazine and Bitcoin.com News. Bitcoin Magazine also reported that the project disabled instances on its hosted service.
Reports documented unauthorized account creation and fund withdrawals. Kevin Ravensberg, who runs the Telegram tipping service BitTipBot on an LNbits instance, said attackers created new accounts and withdrew 2,285,545 satoshis (about 0.0229 BTC) between roughly 09:22 and 14:00 UTC on November 8, according to both outlets.
LNbits has not published a total of funds lost across affected servers, and no CVE has been issued. The project said it will release full details of the exploit in a separate report.
What operators are told to do
In its upgrade guidance, LNbits warned that "credentials exposed before the upgrade may still give an attacker access afterwards," so installing 1.7.0 is not enough on its own. The recommended steps are:
If a compromise is suspected, set up a fresh server with 1.7.0 instead of only updating the old one, and keep relevant logs before replacing it.
Reset all user wallet keys from the Super Admin settings; existing keys stop working and connected apps need the new keys.
Revoke and replace funding-source credentials, such as API keys or macaroons, and update them in LNbits.
Treat any other secrets stored in LNbits settings as compromised and replace them.
Delete and recreate extension connections for NWC Provider, LNDHub, Bolt Cards, TPOS, Bleskomat and FOSSA.
What else is in 1.7.0
The GitHub release notes describe security hardening across authentication, extension management and payment handling, along with dependency updates. The version also adds new features, including TOTP two-factor authentication, on-chain wallet support, BOLT12 offer payments, NIP-17 support, a job scheduler, automatic extension updates and a superuser option to reset all wallet keys.
Hot wallet risk
LNbits reminded operators that it works as a hot wallet, meaning the credentials needed to spend funds sit on an online system. The project advised keeping only the funds needed for day-to-day operations online, reviewing balances and outgoing payments regularly, and moving excess funds to an on-chain wallet whose spending keys are kept offline.
Sources & further reading
See the signals and their results
Browse publicly logged signals and how they performed, or create a free account to follow them.





