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 43 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 candidatefeat: UI for credetials update threshold (#4136)by Vlad Stan · ee74ed29 · Aug 31, 2026 · 3 filesMessage 65 · AdequateLow 45Details
Commit message · Vlad Stan

feat: UI for credetials update threshold (#4136)

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
authentication path
AI analysis · Low 45/100

This commit adds a user-interface setting for a 'credentials update threshold' and, more importantly, fixes a security gap in the authentication cache. Previously, when a user's login was cached for performance, API-token permissions were not re-checked on every request. That meant a cached session could continue using an API token even after the token had been deleted or its permissions had been reduced. The patch now re-validates the API token's permissions on each cached request and adds tests to prove it.

Security candidatefix: forward ip (#4132)by Vlad Stan · 4109aa1f · Aug 25, 2026 · 33 filesMessage 48 · ThinHigh 75Details
Commit message · Vlad Stan

fix: forward ip (#4132)

48/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · High 75/100

This commit is a large security-focused patch for LNbits. It replaces the external library's LNURL handling with custom code that validates URLs, blocks private/internal IP addresses by default, limits redirects, and prevents credential leaks. It also hardens webhooks, login throttling, database backup commands, callback URL checks, and fixes Stripe/PayPal currency handling. The default authentication method is changed to username+password only, removing the weaker 'user-id-only' default.

Security candidateUsers should be allowed to downgrade payout permission (#4083)by Arc · b15478ac · Jul 27, 2026 · 2 filesMessage 73 · AdequateLow 26Details
Commit message · Arc

Users should be allowed to downgrade payout permission (#4083)

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

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
update trustcredential or privilege state
AI analysis · Low 26/100

This commit updates minified JavaScript files related to extension components in LNbits. The visible title suggests it allows users to 'downgrade payout permission' for extensions. The actual diff is a large minified bundle change that is hard to read, and no clear security-relevant code pattern is directly visible. It likely fixes a UI/permission workflow issue where users could not reduce an extension's payout permission level.

Security candidatefeat: add wasm manifest (#4089)by Vlad Stan · 8723d327 · Jul 24, 2026 · 19 filesMessage 65 · AdequateLow 31Details
Commit message · Vlad Stan

feat: add wasm manifest (#4089)

Co-authored-by: Arc <ben@arc.wales>

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
authentication path
AI analysis · Low 31/100

This commit adds support for a new category of browser-based extensions ('WASM extensions') in LNbits. It introduces a second manifest list, fetches extra configuration from URLs, and wires up permission checks before installing these extensions. There is no clear security bug in the diff, but the change expands the attack surface by adding a new extension type and by fetching remote config files. The code also contains a small duplication bug where the WASM manifest list is added twice in one place, which is likely harmless but shows the patch is fresh and partially incomplete.

Security candidatetests: wasm UI tests (#4090)by Vlad Stan · c0806ca5 · Jul 24, 2026 · 18 filesMessage 63 · AdequateInformational 15Details
Commit message · Vlad Stan

tests: wasm UI tests (#4090)

63/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit adds a new automated browser testing suite for LNbits. It introduces Playwright-based end-to-end tests, a GitHub Actions workflow, helper scripts, and dependency updates. There are no changes to production application code, no bug fixes, and no security patches visible in the diff.

Security candidatefix: sso missing user id (#4082)by Vlad Stan · eee372bb · Jul 22, 2026 · 2 filesMessage 65 · AdequateLow 35Details
Commit message · Vlad Stan

fix: sso missing user id (#4082)

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
authentication path
AI analysis · Low 35/100

This commit fixes a bug in LNbits' single-sign-on (SSO) login code. The login endpoint required callers to supply a 'user_id' value, but in normal use it should be optional. Without the fix, users trying to log in via an external provider such as Keycloak would hit an error because the parameter was missing. The change makes the parameter optional by giving it a default value of None, and adds a test that confirms the redirect to the SSO provider still works when no user_id is supplied.

Security candidatefeat: display expiration for ACL tokens (#4033)by Tiago Vasconcelos · 20115b42 · Jul 21, 2026 · 8 filesMessage 80 · StrongInformational 19Details
Commit message · Tiago Vasconcelos

feat: display expiration for ACL tokens (#4033)

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

80/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
Why it was queued
authentication path
AI analysis · Informational 19/100

This commit is a small user-interface feature: it adds an 'expires at' timestamp to API access-control tokens so users can see when each token will expire. The backend now stores the expiration time when a token is created, and the account page displays it. There is no obvious security vulnerability in the change itself; it is purely informational.

Security candidatefeat: keep funding source on default reset, force seed backup (#4040)by Arc · 7eb99652 · Jul 8, 2026 · 13 filesMessage 70 · AdequateLow 32Details
Commit message · Arc

feat: keep funding source on default reset, force seed backup (#4040)

Co-authored-by: alan <alan@lnbits.com>

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
seed or entropy pathsigning or wallet path
AI analysis · Low 32/100

This commit changes how LNbits resets its admin settings to factory defaults. Previously, clicking 'restore defaults' would wipe all core settings except the super-user ID and web-push keys. After this change, it also preserves every configured funding-source setting (wallet connections to Lightning nodes/exchanges) and adds UI prompts that force the admin to confirm they have backed up the seed phrase for certain funding sources before saving. The change reduces the chance that an admin accidentally locks themselves out of their money by resetting settings, and it nudges admins to back up recovery phrases.

Security candidatefix: do not hit sso provider on user missmatch (#3995)by Vlad Stan · 564edfc4 · Jun 3, 2026 · 2 filesMessage 70 · AdequateModerate 59Details
Commit message · Vlad Stan

fix: do not hit sso provider on user missmatch (#3995)

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
authentication path
AI analysis · Moderate 59/100

This patch fixes a security gap in LNbits' single-sign-on (SSO) login flow. Previously, an attacker could start an SSO login for someone else's user ID, potentially tricking the system into linking an external identity to an account they do not own. The fix now checks that the requested user ID matches the currently authenticated user before redirecting to the SSO provider. The commit message and tests confirm the issue was a 'user mismatch' that caused an unwanted SSO-provider hit.

Security candidatefix: OIDC SSO login issues. closes #3970 (#3979)by dni ⚡ · 8f033a60 · May 20, 2026 · 1 fileMessage 65 · AdequateLow 48Details
Commit message · dni ⚡

fix: OIDC SSO login issues. closes #3970 (#3979)

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
authentication path
AI analysis · Low 48/100

This commit fixes an OpenID Connect (OIDC) single sign-on login bug. Previously, when a user logged in via SSO without an existing account link, the code tried to decrypt a value that was actually the string 'null', which would fail and block login. The fix treats 'null' or missing state as having no user ID, allowing login to proceed normally. This is a reliability fix; there is no direct evidence in the commit that it fixes a security vulnerability.

Security candidatefix: first_install for local (#3927)by Arc · 385fb4f9 · Apr 14, 2026 · 2 filesMessage 65 · AdequateLow 42Details
Commit message · Arc

fix: first_install for local (#3927)

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
authentication path
AI analysis · Low 42/100

This commit changes LNbits so that, by default, login cookies are no longer marked 'Secure' (which normally forces HTTPS). The change is intentional to keep fresh local HTTP installs working out of the box, but it means a default installation on plain HTTP will send session cookies over unencrypted connections. An attacker on the same network could potentially sniff or steal those cookies and impersonate the admin. The patch also adds tests confirming the new default behavior and that the secure flag is only added when an operator explicitly enables it.

Security candidate[test] Codex tests (#3911)by Vlad Stan · 183e6e56 · Mar 31, 2026 · 40 filesMessage 53 · ThinInformational 19Details
Commit message · Vlad Stan

[test] Codex tests (#3911)

53/100 · ThinMessage clarity
✓ Descriptive subject✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathauthentication path
AI analysis · Informational 19/100

This commit is almost entirely a large batch of new and updated automated tests for the LNbits project. It also makes one tiny production code change: the timestamp field in the TinyURL data model is switched from a plain number to a proper UTC datetime with a default value. There is no obvious security vulnerability being introduced or fixed here; the main effect is to improve test coverage and make the test setup slightly more reliable.

Security candidate[feat] reset the first install token (#3894) (#3898)by dni ⚡ · 15faab4f · Mar 25, 2026 · 7 filesMessage 73 · AdequateLow 44Details
Commit message · dni ⚡

[feat] reset the first install token (#3894) (#3898)

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

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
authentication path
AI analysis · Low 44/100

This commit adds a safety feature for LNbits that detects when the 'first install token' (a secret used during initial setup) has changed. If it changes after the first install is complete, the system resets the superuser setup so the new token must be used. This is a defensive hardening change, not an active vulnerability fix, though it addresses a scenario where an old token could otherwise remain valid.

Security candidate[feat] configure HTTPS Only settings (#3801)by Vlad Stan · bbad4a91 · Mar 23, 2026 · 4 filesMessage 53 · ThinLow 36Details
Commit message · Vlad Stan

[feat] configure HTTPS Only settings (#3801)

53/100 · ThinMessage clarity
✓ 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 · Low 36/100

This commit adds a new configuration option that lets LNbits administrators decide whether authentication cookies must only be sent over HTTPS and whether single-sign-on (SSO) should reject plain HTTP connections. By default the setting is turned on, which improves security for production deployments. The change also fixes a related bug where SSO login responses did not include the user's account ID in the access token. Test and CI configurations explicitly disable the HTTPS-only requirement so automated tests can run without TLS.

Security candidatefeat: Add generic OIDC authentication provider (#3760)by satcat21 · 3398070d · Mar 23, 2026 · 35 filesMessage 75 · AdequateLow 31Details
Commit message · satcat21

feat: Add generic OIDC authentication provider (#3760)

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 controlauthentication path
AI analysis · Low 31/100

This commit adds a new 'Login via OIDC' option to LNbits, similar to existing 'Login with Google/GitHub' buttons. It lets server admins connect LNbits to any standard OpenID Connect identity provider (like Zitadel, Authentik, Okta). The change is a feature addition: new settings, a new Python SSO class, UI labels, and documentation. There is no direct evidence in the commit of a security vulnerability, but any new authentication path can introduce risks if configured or implemented poorly.

Security candidateCI: pin boltz to version (#3852)by dni ⚡ · 8bcf5e4f · Mar 5, 2026 · 2 filesMessage 65 · AdequateInformational 18Details
Commit message · dni ⚡

CI: pin boltz to version (#3852)

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
access control
AI analysis · Informational 18/100

This commit only changes the local development/testing setup for LNbits. It pins the Boltz service used in CI/regtest from the floating 'latest' Docker tag to a specific version (v3.12.1), and updates the matching test configuration file. There is no change to production LNbits code, no user-facing fix, and no disclosed security issue.

Security candidatefix: `/first_install` new superuser may duplicate an username (#3787)by dni ⚡ · 4894b70b · Feb 25, 2026 · 1 fileMessage 70 · AdequateLow 46Details
Commit message · dni ⚡

fix: `/first_install` new superuser may duplicate an username (#3787)

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
authentication path
AI analysis · Low 46/100

This patch fixes a setup-time bug in LNbits where the initial superuser account could be assigned a username that already belongs to another user. Before the fix, the first-install endpoint did not check for duplicate usernames, which could create account confusion or allow the new admin to overlap with an existing user's identity. The patch now rejects the request if the chosen username is already taken.

Security candidate[feat] User invitation code (#3761)by Vlad Stan · e286546b · Feb 25, 2026 · 16 filesMessage 53 · ThinLow 27Details
Commit message · Vlad Stan

[feat] User invitation code (#3761)

53/100 · ThinMessage clarity
✓ 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 · Low 27/100

This commit adds a new optional 'invitation code' feature for user registration in LNbits. It allows administrators to require an activation code before a new user can register. The feature is disabled by default and only takes effect when an admin explicitly turns it on. There is no direct evidence in the commit of a security vulnerability being fixed; it appears to be a new access-control feature.

Security candidate[feat] User activation (#3749)by Vlad Stan · 7e327b2c · Feb 25, 2026 · 16 filesMessage 43 · ThinLow 46Details
Commit message · Vlad Stan

[feat] User activation (#3749)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication path
AI analysis · Low 46/100

This commit adds a new 'user activation' feature to LNbits. It introduces an 'activated' flag on every user account, lets administrators deactivate or reactivate users, and blocks deactivated users from logging in or accessing wallets via API keys. The change is a security/administrative control rather than a fix for an active vulnerability, but it changes who can access the system and how authentication checks work.

Security candidatefeat: FIRST_INSTALL_TOKEN to help services like Umbrel secure the first_install endpoint (#3751)by Arc · 40c055e3 · Feb 25, 2026 · 10 filesMessage 85 · StrongModerate 58Details
Commit message · Arc

feat: FIRST_INSTALL_TOKEN to help services like Umbrel secure the first_install endpoint (#3751)

Co-authored-by: dni ⚡ <office@dnilabs.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 · Moderate 58/100

This commit adds an optional FIRST_INSTALL_TOKEN setting to LNbits. When configured, anyone trying to complete the initial superuser setup on the /first_install page must provide the correct token. Without the token, the setup request is rejected. This is a defensive hardening feature, not a vulnerability fix, aimed at platforms like Umbrel that expose LNbits during automated setup.

Security candidate[feat] persist user ui customization (#3743)by Vlad Stan · e72396fe · Feb 25, 2026 · 16 filesMessage 53 · ThinInformational 18Details
Commit message · Vlad Stan

[feat] persist user ui customization (#3743)

53/100 · ThinMessage clarity
✓ 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 · Informational 18/100

This commit adds a feature to save a user's visual preferences (theme, language, etc.) on the server so they persist across devices. It introduces a new authenticated API endpoint that stores a JSON blob in the user's account record. The change is a feature addition, not a security fix, and the main risk is that the endpoint accepts arbitrary JSON and merges it into the account with only a size limit for protection.

Security candidate[feat] admin impersonate user (#3741)by Vlad Stan · 9be894da · Feb 25, 2026 · 13 filesMessage 53 · ThinModerate 63Details
Commit message · Vlad Stan

[feat] admin impersonate user (#3741)

53/100 · ThinMessage clarity
✓ 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 commit adds an 'admin impersonate user' feature to LNbits. It allows an administrator to log in as another non-admin user by providing that user's ID. The feature is gated behind admin checks and stores the admin's original token in a separate cookie so the admin can later stop impersonating and return to their own session. The change is a deliberate feature, not a hidden backdoor, but it does expand what an admin account can do and could be abused if an admin's session is compromised.

Security candidatefix: better validation error messages (#3736)by Vlad Stan · 67bb86c1 · Feb 25, 2026 · 5 filesMessage 65 · AdequateInformational 19Details
Commit message · Vlad Stan

fix: better validation error messages (#3736)

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
authentication path
AI analysis · Informational 19/100

This commit changes how LNbits reports validation errors to users. Previously, the API returned a plain string summary of the error. Now it returns a structured list of individual validation failures. This is a user-experience improvement that makes error messages clearer, but it does not fix a security vulnerability and does not introduce a clear one. The main side effect is that error responses now expose slightly more internal detail about which fields failed validation and why.

Security candidateperf: use `check_account_exists` decorator (#3600)by Vlad Stan · b3efb4d3 · Dec 4, 2025 · 12 filesMessage 70 · AdequateLow 34Details
Commit message · Vlad Stan

perf: use `check_account_exists` decorator (#3600)

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 34/100

This commit is a performance refactor that replaces a heavier 'check the full user object' dependency with a lighter 'check the account exists' dependency across many API endpoints. It also adds a short-lived cache for authentication lookups. The change is not described as a security fix, but it does touch access-control code, so it needs careful review. There is no direct evidence in the commit of a vulnerability being introduced or fixed.

Security candidate[feat] Payment labels (#3537)by Vlad Stan · 7c7a04da · Nov 21, 2025 · 26 filesMessage 43 · ThinInformational 20Details
Commit message · Vlad Stan

[feat] Payment labels (#3537)

43/100 · ThinMessage clarity
✓ Descriptive subject✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 20/100

This commit adds a new 'payment labels' feature to LNbits, allowing users to tag and filter their payments. It also makes a small change so the app's logo is loaded from the local server instead of an external CDN. The changes are mostly routine feature work, but one part of the code uses a LIKE-based search on stored label data that could, in theory, be tricked into matching unintended records if an attacker can control label values. There is no clear evidence this is exploitable as a practical attack, and the commit does not describe itself as a security fix.