LN
← All projectsLNbits

LNbits

Self-hosted Lightning wallet, accounts, payment API, and extension platform supporting multiple funding sources.

BitcoinLightning NetworkPayment infrastructureActive incident
Repository coverage

598 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

51security candidates144second-pass queue196AI analyses
63commits · 30 days
141commits · 60 days
291commits · 180 days
547commits · 365 days
Backfill bands
Nov 8 → May 12291 seen16 candidatesComplete
May 12 → Sep 9146 seen12 candidatesComplete
Sep 9 → Oct 932 seen6 candidatesComplete
Oct 9 → Nov 899 seen10 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

71/100 average clarity
171Strong · 80–100
341Adequate · 60–79
80Thin · 40–59
6Opaque · 0–39
2security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Vlad Stan1372758564
Arc631127366
Riccardo Balbo403140
dni ⚡185558069
Tiago Vasconcelos38311068
monasco622053
Bitkarrot624085
satcat21111075
dependabot[bot]6400093
blackcoffeexbt1005065
Nathan Day904086
Bartok802081
Analysis record

Published AI watches

Last scanned 47 minutes ago

Low 41 AI analysisMessage 73 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat (wasm): Adds csv/print to wasm iframes, core theme passing, optional unhashed description, scoped invoice status, fiat checkout and browser storage (#4328)

This commit adds several new features to LNbits' WebAssembly (WASM) extension system. It introduces ways for extensions to: check invoice status, refresh payment status, create fiat checkout invoices, store small amounts of data in the bro…

Untrusted `extension_context` dictionary replaced by frozen typed model `PaymentExtensionContext` with required `extension_id`, `owner_id`, `wallet_id`, and optional `source_id`.New `wallet.invoice_status` method enforces strict binding checks (extension, owner, wallet, source) before returning only `paid/pending/failed/amount-msat`; rejects legacy/unbound invoices.New `wallet.refresh_payment` requires authentication, wallet ownership or shared-wallet VIEW_PAYMENTS permission, and scopes payment lookup by wallet; hides backend error details.
df3a180aby Arc+1919−8322 files
No security note in commit
Moderate 63 AI analysisMessage 58 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix[8c7f]: reject SSO for accounts with passwords (#4347)

This update blocks users from logging into password-protected accounts through single sign-on (SSO), such as 'Login with GitHub'. Before this change, an attacker who knew or guessed a victim's email address could potentially use an SSO pro…

Authentication bypass mitigation: SSO can no longer authenticate accounts that also have local passwordsAccount takeover risk reduction: blocks an external identity provider from overriding a password-protected accountState preservation: password hash and email_verified flag remain unchanged on rejection
b1d22089by Vlad Stan+70−23 files
No security note in commit
Low 44 AI analysisMessage 58 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix[8c7f]: keep unrecorded Core Lightning payments pending (#4345)

This commit changes how LNbits interprets a missing Core Lightning payment record. Previously, if no payment record existed, LNbits marked the payment as failed. Now it marks it as still pending, because a payment that is currently being s…

Change in payment state machine: empty result now treated as pending rather than failedPotential race condition between payment initiation and status pollingRisk of duplicate payment attempts if pending status leads to retries
49755d33by Vlad Stan+2−21 file
No security note in commit
High 81 AI analysisMessage 75 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: reject user ID authentication for password accounts (#4340)

This commit fixes an authentication bypass in LNbits. Previously, an account that had been created without a password could still be logged into using only the user ID even after a password was later added. An attacker who knew (or guessed…

Authentication bypass via user ID for password-protected accountsStale authentication cache could grant access after password upgradeNew guard `check_passwordless_account` enforces password requirement
db9563d2by Vlad Stan+196−448 files
Vendor flagged security relevance
Moderate 67 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: respect shared wallet permissions for payment updates (#4338)

This commit fixes a permission bug in LNbits where users of shared wallets could update or settle/cancel payments even when they only had view-only access. It also adds a check so that settle/cancel actions only work on special 'hold invoi…

Access-control bypass fix for shared wallet payment updatesNew permission check can_update_payments() tied to shared wallet receive/send permissionsNew hold_invoice guard on settle/cancel endpoints
d718f9aeby Vlad Stan+154−64 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

chore: remove extension builder from core (#4331)

This commit completely removes the 'Extension Builder' feature from LNbits core. It deletes the backend code that generated extensions from templates, the API endpoints, the web UI pages, and related settings. There is no bug being fixed a…

Removal of a code-generation feature that used Jinja2 with autoescape=False (bandit S701 was previously suppressed for this file)Removal of an endpoint that allowed admins to build, deploy, and activate extensions from user-supplied JSON configurationReduction of extension installation attack surface by removing the builder manifest source and preview file-serving route
c8d47013by Vlad Stan+14−334535 files
No security note in commit
Low 49 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: disable paid reviews (#4325)

This update turns off a default paid-extension review service in LNbits. It stops the wallet from automatically contacting a third-party payment/review server when it lists or updates extensions, and resets the default review URL to empty.…

Default third-party review/payment URL removedMigration forcibly resets stored review URL to emptyBackground extension update/install no longer queries remote pay_link for pricing
77cc2276by Vlad Stan+208−1313 files
No security note in commit
Moderate 60 AI analysisMessage 55 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: packaging/builds (#4319)

This commit fixes a packaging/build issue in LNbits, but the code changes also harden how sensitive funding-source settings (wallet seeds, API keys, macaroons) are exposed and edited through the admin web interface. Previously, non-super a…

Authorization boundary tightened: funding-source credentials restricted to superuser in API and UISeed-integrity check added: configured mnemonic must match persisted seed.dat before settings are writtenBackup confirmation reset when funding seed changes, preventing silent wallet substitution
fe2b0a98by Arc+913−6918 files
No security note in commit
Critical 100 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat: Add superuser action to reset all wallet keys (#4320)

This commit adds a recovery feature that lets the LNbits superuser instantly replace every wallet's secret keys, including keys for deleted wallets, and clear any cached copies of the old keys. The vendor says this is needed because of a r…

Vendor describes the change as a recovery control for a security incident involving exposed wallet credentialsVendor states all versions before 1.7.0 are affected and funds are at risk of theftNew superuser-only endpoint can rotate every wallet's admin and invoice keys, including deleted wallets
45a25b24by Vlad Stan+523−58 files
Vendor flagged security relevance
Moderate 63 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat: Automatically update extensions on startup and on a schedule (#4314)

This commit adds an automatic extension update feature to LNbits. By default, it checks for and installs newer versions of installed extensions when the server starts, and can repeat that check every 24 hours. Because extensions are downlo…

Automatic download and execution of third-party code is enabled by defaultUpdate source is the extension's configured source_repo, not a vendor-curated storeNo code signature or hash verification is visible in the diff beyond existing archive validation helpers
a16d7752by Vlad Stan+836−1511 files
No security note in commit
Critical 89 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: harden SSRF checks and use explicit local LNURL route opt-ins (#4313)

This commit is a security hardening patch for LNbits, a Bitcoin Lightning wallet platform. It fixes weaknesses in the server's outgoing web-request protections (SSRF, or Server-Side Request Forgery) that could let an attacker trick the LNb…

SSRF hardening: multicast, IPv6 transition/embedded addresses, and EC2 IPv6 metadata endpoint blockedLocal LNURL routing moved from hard-coded regex allow-list to explicit per-route openapi_extra opt-inBackslash path traversal blocked in private HTTP endpoint checks
fc5e0b60by Arc+168−408 files
Vendor flagged security relevance
Critical 90 AI analysisMessage 85 · Strong
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: centralize SSRF protection and block self-targeted requests (#4310)

This is a major security patch for LNbits released after a November incident. It fixes two broad weaknesses: attackers could trick the server into making requests to itself or to internal/cloud services (SSRF), and new user accounts could …

New centralized SafeHttpClient with DNS pinning, redirect limits, and destination validationNew outbound.py blocks requests to the instance hostname and locally assigned/supplied IP addressesSSRF protection applied to LNURL, NIP-05, webhooks, WASM extension HTTP, and WebSockets
7a176c59by Arc+2076−30332 files
Vendor flagged security relevance
Low 35 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix(corelightningrest): compute payment status fee as sent minus amount (#4300)

This commit fixes a bug in how LNbits calculates the fee for a completed Core Lightning REST payment. The old code incorrectly subtracted a negative 'amount sent' value, which produced the wrong fee. The fix changes the formula so the fee …

Incorrect arithmetic in financial/fee calculationTest fixture updated to match corrected sign conventionWallet backend payment status logic changed
45a8704fby Amartya Vikram Singh+2−22 files
No security note in commit
Moderate 52 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: ignore failed payments in daily withdraw limit (#4297)

This commit fixes a bug in LNbits where failed outgoing payments were incorrectly counted against a wallet's daily withdrawal limit. Because failed payments never actually moved money out of the wallet, counting them could wrongly block le…

Business-logic flaw in access-control / spending limitIncorrect state filter on financial transaction queryDenial-of-service-like effect: legitimate withdrawals blocked by stale failed payment records
206477d4by Amartya Vikram Singh+54−02 files
No security note in commit
Low 34 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix(lnpay): return checking_id from create_invoice (#4295)

This commit fixes a bug in the LNPay wallet integration where newly created Lightning invoices were not returning their internal tracking ID ('checking_id'). Without this ID, LNbits could not reliably match future payment updates to the co…

Missing correlation identifier in payment responsePotential invoice state desynchronization between LNbits and LNPay backendRegression test added for payment identifier handling
918b38dcby Amartya Vikram Singh+22−02 files
No security note in commit
Moderate 60 AI analysisMessage 70 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: prevent duplicate BOLT12 offer payments on retry (#4287)

This commit fixes a bug where retrying a BOLT12 offer payment could accidentally pay the same offer twice. It adds an idempotency check using an external_id so that retries return the original payment instead of creating a duplicate, while…

Duplicate payment prevention for BOLT12 offersIdempotency keyed on wallet_id + external_idConflict detection when external_id reused with different payment details
ea2686d1by Vlad Stan+426−89 files
No security note in commit
High 79 AI analysisMessage 55 · Thin
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: mempool urls (#4286)

This commit fixes a security gap in LNbits' on-chain (Bitcoin) wallet feature. Previously, a wallet owner could point their wallet at any Mempool-style block explorer URL, including internal or attacker-controlled addresses. The server wou…

Server-Side Request Forgery (SSRF) mitigation: unapproved mempool endpoints are rejected before httpx.AsyncClient is instantiatedOpen redirect / redirect-to-attacker mitigation: follow_redirects=False on mempool requestsInput validation: Pydantic validator strips paths, rejects credentials, fragments, query strings, control chars, backslashes, and invalid ports
f9dd17f3by Vlad Stan+354−2212 files
Vendor flagged security relevance
Low 45 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

fix: payment ws notifications (#4282)

This commit fixes how LNbits notifies the user interface about incoming Lightning payments. Previously, the same paid invoice could be processed and announced multiple times, causing duplicate or confusing wallet notifications. The change …

Race condition in payment status update between polling loop and paid-invoice streamDuplicate WebSocket notifications for the same settled invoiceRefactoring to atomic DB-lock guarded update of incoming payment status
aa041306by Vlad Stan+388−297 files
No security note in commit
Low 39 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

chore: bump to pydantic 2 (#4253)

This is a large dependency upgrade from Pydantic 1 to Pydantic 2 across the LNbits project. Most changes are mechanical renames (e.g., dict() to model_dump(), parse_obj() to model_validate()). A few small functional changes are mixed in: i…

Dependency major-version upgrade (Pydantic 1 -> 2) with broad validation behavior changesRemoval of Pydantic v1 duplicate-validator cache workaround in extension route registrationJWT account resolution reordered to prefer 'usr' claim over 'sub' claim
2ab7662eby Vlad Stan+1548−753119 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
LN LNbitsLNbits BitcoinLightning NetworkPayment infrastructure

feat: make onchain dialog more readeable (#4269)

This commit is a user-interface redesign of the on-chain Bitcoin receive dialog. It splits the dialog into two screens: one to enter an amount and note, and another to display the QR code. The changes are purely cosmetic and do not alter h…

0e0ee6edby Tiago Vasconcelos+144−804 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Security candidatefix[8c7f]: reject SSO for accounts with passwords (#4347)by Vlad Stan · b1d22089 · Nov 17, 2026 · 3 filesMessage 58 · ThinModerate 63Details
Commit message · Vlad Stan

fix[8c7f]: reject SSO for accounts with passwords (#4347)

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Moderate 63/100

This update blocks users from logging into password-protected accounts through single sign-on (SSO), such as 'Login with GitHub'. Before this change, an attacker who knew or guessed a victim's email address could potentially use an SSO provider to access an account that also had a password, possibly bypassing the password (and any two-factor authentication tied to it). The fix makes the system reject SSO logins for any account that has a password set, forcing password-based login instead.

Security candidatefix: reject user ID authentication for password accounts (#4340)by Vlad Stan · db9563d2 · Nov 17, 2026 · 8 filesMessage 75 · AdequateHigh 81Details
Commit message · Vlad Stan

fix: reject user ID authentication for password accounts (#4340)

75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access controlsigning or wallet pathauthentication path
AI analysis · High 81/100

This commit fixes an authentication bypass in LNbits. Previously, an account that had been created without a password could still be logged into using only the user ID even after a password was later added. An attacker who knew (or guessed) the user's ID could access the account and wallets without needing the password. The patch now rejects user-ID-only login for any account that has a password set.

Security candidatefix: respect shared wallet permissions for payment updates (#4338)by Vlad Stan · d718f9ae · Nov 16, 2026 · 4 filesMessage 70 · AdequateModerate 67Details
Commit message · Vlad Stan

fix: respect shared wallet permissions for payment updates (#4338)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
credential or privilege statesigning or wallet path
AI analysis · Moderate 67/100

This commit fixes a permission bug in LNbits where users of shared wallets could update or settle/cancel payments even when they only had view-only access. It also adds a check so that settle/cancel actions only work on special 'hold invoices,' preventing them from being misused on regular payments. The change is a security fix for access control.

Security candidatefix: disable paid reviews (#4325)by Vlad Stan · 77cc2276 · Nov 11, 2026 · 13 filesMessage 65 · AdequateLow 49Details
Commit message · Vlad Stan

fix: disable paid reviews (#4325)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Low 49/100

This update turns off a default paid-extension review service in LNbits. It stops the wallet from automatically contacting a third-party payment/review server when it lists or updates extensions, and resets the default review URL to empty. It also renames the local auth key file so a fresh key is generated, which helps avoid reusing a potentially exposed key. The changes are defensive: they reduce the chance that a compromised or malicious review server could trick users into paying for extensions or leak information about installed extensions.

Security candidatefix: packaging/builds (#4319)by Arc · fe2b0a98 · Nov 10, 2026 · 18 filesMessage 55 · ThinModerate 60Details
Commit message · Arc

fix: packaging/builds (#4319)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Moderate 60/100

This commit fixes a packaging/build issue in LNbits, but the code changes also harden how sensitive funding-source settings (wallet seeds, API keys, macaroons) are exposed and edited through the admin web interface. Previously, non-super admin users could read and modify these credentials; now only the superuser can. The patch also prevents the desktop launcher from accidentally overwriting or leaking wallet seeds when switching funding providers, and it stops startup if the saved seed does not match the configured one. These are defensive security improvements rather than a reported vulnerability fix.

Security candidatefeat: Automatically update extensions on startup and on a schedule (#4314)by Vlad Stan · a16d7752 · Nov 10, 2026 · 11 filesMessage 70 · AdequateModerate 63Details
Commit message · Vlad Stan

feat: Automatically update extensions on startup and on a schedule (#4314)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Moderate 63/100

This commit adds an automatic extension update feature to LNbits. By default, it checks for and installs newer versions of installed extensions when the server starts, and can repeat that check every 24 hours. Because extensions are downloaded from external repositories and installed without a human reviewing the code, a compromised extension publisher or repository could push malicious code that LNbits would automatically run. The commit does include safeguards—only stable releases from the same source repo, version compatibility checks, and permission checks for WebAssembly extensions—but the feature is enabled by default and relies on the security of third-party extension sources.

Security candidatefix: centralize SSRF protection and block self-targeted requests (#4310)by Arc · 7a176c59 · Nov 9, 2026 · 32 filesMessage 85 · StrongCritical 90Details
Commit message · Arc

fix: centralize SSRF protection and block self-targeted requests (#4310)

Co-authored-by: Vlad Stan <stan.v.vlad@gmail.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
authentication path
AI analysis · Critical 90/100

This is a major security patch for LNbits released after a November incident. It fixes two broad weaknesses: attackers could trick the server into making requests to itself or to internal/cloud services (SSRF), and new user accounts could be created too freely, letting attackers sign up and abuse those features. The patch centralizes outbound-request protections, blocks self-targeted requests, disables public registration by default, and adds activation/invitation requirements. The vendor explicitly says every version before 1.7.0 is affected and funds are at risk of theft.

Security candidatefix: payment ws notifications (#4282)by Vlad Stan · aa041306 · Nov 2, 2026 · 7 filesMessage 65 · AdequateLow 45Details
Commit message · Vlad Stan

fix: payment ws notifications (#4282)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Low 45/100

This commit fixes how LNbits notifies the user interface about incoming Lightning payments. Previously, the same paid invoice could be processed and announced multiple times, causing duplicate or confusing wallet notifications. The change centralizes the 'mark as paid' logic under a database lock and only queues one WebSocket notification per invoice. There is no direct evidence in the commit of a security vulnerability such as theft of funds, but duplicate notifications could mislead users or downstream systems and the race condition hints at possible state inconsistencies.

Security candidatechore: bump to pydantic 2 (#4253)by Vlad Stan · 2ab7662e · Oct 29, 2026 · 119 filesMessage 65 · AdequateLow 39Details
Commit message · Vlad Stan

chore: bump to pydantic 2 (#4253)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 39/100

This is a large dependency upgrade from Pydantic 1 to Pydantic 2 across the LNbits project. Most changes are mechanical renames (e.g., dict() to model_dump(), parse_obj() to model_validate()). A few small functional changes are mixed in: invoice creation now explicitly rejects missing amounts, daily withdrawal limit checks are paginated and abort on shutdown, JWT account lookup now checks usr before sub, and validation error responses no longer include raw user input. The commit does not describe itself as a security fix, but the upgrade removes a known Pydantic 1 validator cache workaround and may affect input validation behavior across the API.

Security candidatefix: invalidate jwt token on password reset (#4248)by Vlad Stan · 84242e41 · Oct 15, 2026 · 5 filesMessage 70 · AdequateModerate 60Details
Commit message · Vlad Stan

fix: invalidate jwt token on password reset (#4248)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
defensive validationauthentication path
AI analysis · Moderate 60/100

This commit fixes a security bug in LNbits where changing or resetting a user's password did not automatically log out active sessions. Before the fix, someone who stole or shared a login session could keep using it even after the password was changed, because the system only checked two-factor authentication revisions, not password changes. The patch now bumps a hidden 'session revision' whenever the password changes, so all existing tokens and browser cookies are rejected and the user must log in again.

Security candidatefeat: add TOTP two-factor authentication (#4203)by Vlad Stan · b88dd08b · Oct 15, 2026 · 34 filesMessage 85 · StrongInformational 15Details
Commit message · Vlad Stan

feat: add TOTP two-factor authentication (#4203)

Co-authored-by: Arc <33088785+arcbtc@users.noreply.github.com>

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controlauthentication path
AI analysis · Informational 15/100

This commit adds a new optional TOTP two-factor authentication feature to LNbits. It is a security-hardening feature, not a vulnerability fix or an introduced flaw. The code introduces encryption for TOTP secrets, recovery codes, rate limiting on verification attempts, and enforcement of 2FA at login and for sensitive operations. There is no evidence in the commit of a security bug, backdoor, or bypass.

Security candidatefix account panel text overflow (#4218)by Tiago Vasconcelos · 78488f70 · Oct 15, 2026 · 1 fileMessage 58 · ThinInformational 15Details
Commit message · Tiago Vasconcelos

fix account panel text overflow (#4218)

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
memory safety
AI analysis · Informational 15/100

This commit is a purely cosmetic UI fix for the account settings page. It adjusts CSS classes and moves the logout button out of the navigation element so that long text in the account panel no longer overflows its container. There is no security relevance.

Security candidatefeat: onchain wallet type (#4194)by Arc · 477ddf3d · Oct 15, 2026 · 110 filesMessage 65 · AdequateModerate 59Details
Commit message · Arc

feat: onchain wallet type (#4194)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update path
AI analysis · Moderate 59/100

This is a large feature commit that adds native Bitcoin on-chain wallet support to LNbits, including hot wallets whose recovery phrases are encrypted by a server-side master key. It introduces new code paths for key management, address derivation, blockchain scanning, transaction signing, and broadcasting. Because the commit is a feature addition rather than a documented security fix, the main risk is that any bugs or design weaknesses in the new on-chain subsystem could lead to loss of funds, key exposure, or incorrect balances. The diff itself does not show an obvious exploitable vulnerability, but the size and sensitivity of the code mean the change should be reviewed carefully before being trusted with real funds.

Security candidatefeat: asset refactor, phoenixd/sparkl2 included, add dmg (#4167)by Arc · 06f940f1 · Oct 15, 2026 · 22 filesMessage 70 · AdequateLow 27Details
Commit message · Arc

feat: asset refactor, phoenixd/sparkl2 included, add dmg (#4167)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 27/100

This commit is a feature release for the LNbits desktop packaging system. It adds bundled 'sidecar' programs (Spark L2 and Phoenixd) that can run a Bitcoin/Lightning wallet alongside LNbits, adds macOS DMG packaging, and includes a small bugfix so failed Spark payments report their actual error message. Most of the change is build/packaging code, not the live LNbits server. The security-relevant parts are: (1) the new code downloads external binaries at build time and checks their SHA256 hashes; (2) it generates and stores wallet seed phrases in a local file; (3) it starts those local wallet processes and talks to them over a loopback port. There is no direct evidence in the commit of an active vulnerability, but the change increases the attack surface of the packaged application because it now ships and runs extra native programs and handles their credentials.

Security candidatefix: paid install QR code never shown for WASM extensions with permissions (#4195)by Bitkarrot · df724585 · Oct 15, 2026 · 2 filesMessage 85 · StrongInformational 17Details
Commit message · Bitkarrot

fix: paid install QR code never shown for WASM extensions with permissions (#4195)

Co-authored-by: bitkarrot <bitkarrot@users.noreply.github.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege state
AI analysis · Informational 17/100

This commit fixes a UI bug where the QR code for paying to install a WASM extension was never shown when the extension required permissions. The change is a one-line JavaScript fix that ensures the permission-grant dialog is closed before the payment QR code is displayed. It is a functional bug fix, not a security vulnerability, but it resolves a workflow issue that could prevent users from completing paid extension installations.

Security candidateMerge commit from forkby monasco · 69879592 · Oct 15, 2026 · 2 filesMessage 28 · OpaqueLow 46Details
Commit message · monasco

Merge commit from fork

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication pathmerge-commit duplicate discount
AI analysis · Low 46/100

This commit adds missing safety checks to two password-related features in LNbits. It now verifies that the new password and its confirmation match, and that chosen usernames follow the allowed format. Previously, these checks were either absent or inconsistent, which could let a user accidentally set a mismatched password or use an invalid username during account setup or password change.

Security candidatefix: invalidate jwt token on password reset (#4248)by Vlad Stan · 181c3ded · Oct 15, 2026 · 5 filesMessage 70 · AdequateHigh 72Details
Commit message · Vlad Stan

fix: invalidate jwt token on password reset (#4248)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
defensive validationauthentication path
AI analysis · High 72/100

This commit fixes a security flaw in LNbits where changing or resetting a user's password did not invalidate existing login sessions. Before the fix, someone who stole or obtained an old access token could keep using it even after the password was changed, because the system did not track that the password had been updated. The patch introduces a 'session revision' that is bumped whenever the password changes, so old tokens and two-factor challenges are rejected.

Security candidatefix account panel text overflow (#4218)by Tiago Vasconcelos · 821d38c0 · Oct 5, 2026 · 1 fileMessage 58 · ThinInformational 15Details
Commit message · Tiago Vasconcelos

fix account panel text overflow (#4218)

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
memory safety
AI analysis · Informational 15/100

This commit is a purely cosmetic UI fix for the account settings page. It adjusts how the left-hand navigation panel is laid out so that long text does not overflow its container. There is no security relevance.

Security candidatefeat: onchain wallet type (#4194)by Arc · 02fce93c · Oct 5, 2026 · 110 filesMessage 65 · AdequateLow 44Details
Commit message · Arc

feat: onchain wallet type (#4194)

65/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update path
AI analysis · Low 44/100

This is a large feature commit that adds native on-chain Bitcoin wallets to LNbits. It introduces new wallet types, address generation, blockchain scanning, transaction signing (including hot wallets), and an encryption key system for recovery phrases. Because this is new code handling real Bitcoin funds and private keys, it carries inherent security risk, but the diff itself does not show an obvious, already-implemented vulnerability. It is a feature addition rather than a documented security fix.

Security candidatefeat: add TOTP two-factor authentication (#4203)by Vlad Stan · 73b83875 · Oct 1, 2026 · 34 filesMessage 85 · StrongInformational 15Details
Commit message · Vlad Stan

feat: add TOTP two-factor authentication (#4203)

Co-authored-by: Arc <33088785+arcbtc@users.noreply.github.com>

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controlauthentication path
AI analysis · Informational 15/100

This commit adds a new optional TOTP two-factor authentication feature to LNbits. It is a security-hardening feature, not a vulnerability fix or an introduced flaw. The code shows careful design: secrets are encrypted, recovery codes are hashed, replay attacks are prevented, brute-force attempts are rate-limited, and audit logs exclude credentials. There is no evidence in the commit of a security bug.

Security candidatefix: paid install QR code never shown for WASM extensions with permissions (#4195)by Bitkarrot · 6e27984f · Sep 21, 2026 · 2 filesMessage 85 · StrongInformational 16Details
Commit message · Bitkarrot

fix: paid install QR code never shown for WASM extensions with permissions (#4195)

Co-authored-by: bitkarrot <bitkarrot@users.noreply.github.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
credential or privilege state
AI analysis · Informational 16/100

This commit fixes a UI bug where the QR code for paying to install a 'WASM' extension was never shown if the extension required special permissions. The change is a one-line logic fix in the JavaScript that controls the extension installation dialog. It is a functional bug fix rather than a security vulnerability, and there is no evidence in the commit of malicious behavior or a disclosed security issue.

Security candidatefeat: asset refactor, phoenixd/sparkl2 included, add dmg (#4167)by Arc · bdd0aa96 · Sep 17, 2026 · 22 filesMessage 70 · AdequateInformational 24Details
Commit message · Arc

feat: asset refactor, phoenixd/sparkl2 included, add dmg (#4167)

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Informational 24/100

This commit is a feature release for the LNbits desktop packaging system. It adds the ability to bundle external Bitcoin/Lightning 'funding' programs (Spark L2 and Phoenixd) directly into the desktop app, adds macOS DMG packaging, and makes a small fix so failed payments report their actual error message. Most of the changes are build scripts, packaging workflows, and tests. There is no obvious remote attack introduced, but the new code does download and execute external binaries, manage wallet seeds, and run local daemons, which increases the app's security surface area.

Security candidateMerge commit from forkby monasco · 69bcd391 · Sep 14, 2026 · 2 filesMessage 28 · OpaqueLow 46Details
Commit message · monasco

Merge commit from fork

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication pathmerge-commit duplicate discount
AI analysis · Low 46/100

This commit adds missing safety checks to two password-related features in LNbits. It now verifies that the new password and its confirmation match, and that chosen usernames follow the allowed format. These are defensive hardening changes rather than fixes for a known active attack, but they close gaps that could let a user accidentally (or via a manipulated client) set a mismatched password or an invalid username during account setup or password change.

Security candidatefix: wallet details (#4153)by Vlad Stan · c888d1f0 · Sep 7, 2026 · 9 filesMessage 55 · ThinModerate 64Details
Commit message · Vlad Stan

fix: wallet details (#4153)

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Moderate 64/100

This commit fixes a privacy and authorization issue in LNbits where wallet secret keys (admin and invoice keys) were being returned to API clients even when the client was authenticated with a restricted access-control token that only had read permission. The change introduces a new helper that masks those keys unless the current request has write access to the endpoint, and applies it to several wallet-listing API responses. It also adds tests confirming the masking behavior.

Security candidatefix: settings ui refector + blockexplorer tweaks (#4144)by Arc · e66236bf · Sep 7, 2026 · 38 filesMessage 85 · StrongLow 27Details
Commit message · Arc

fix: settings ui refector + blockexplorer tweaks (#4144)

Co-authored-by: Tiago Vasconcelos <talvasconcelos@gmail.com>

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
seed or entropy path
AI analysis · Low 27/100

This commit refactors the LNbits settings user interface and makes small adjustments to the built-in Bitcoin block explorer. It adds a new paginated API endpoint for listing transactions inside a block, splits public and authenticated block explorer pages, and introduces a new setting to show the block explorer in the user menu. It also changes the default maximum number of assets per user from 1 to 10. There is no clear security fix or vulnerability being patched in the visible code changes.