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.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
53/100 average clarity
90Strong · 80–100
213Adequate · 60–79
480Thin · 40–59
194Opaque · 0–39
10security candidates with opaque commit messaging
This commit is a simple rename of a code attribute from UseStoreLanguageAttribute to StorefrontRouteAttribute. It only changes the name used in source files and does not alter any program behavior, security settings, or access controls.
This commit changes how the invoice checkout page is translated. Instead of loading translations from separate JSON files in the browser based on a language the customer picks, the page now uses the store's own server-side translation sett…
Removal of client-side language selection reduces attack surface for language-related query-string manipulation (e.g., lang=...)Server-side rendering of checkout strings may reduce exposure to DOM-based XSS via translation files, but no specific vulnerability is shownLarge deletion of locale files and i18next vendor scripts is a cleanup, not a patch
This commit updates two .NET runtime/SDK Docker images to newer patch versions and bumps a third-party library (CsvHelper) from 34.0.0 to 34.1.0. These are routine maintenance updates. The commit message does not say any of the updates fix…
This is a large hardening patch for BTCPay Server that fixes several security weaknesses around account handling, payments, refunds, and plugins. Key changes include: preventing Blazor circuits from staying authenticated after a user's adm…
Blazor circuit principal revalidation against live user stateCookie principal rejection when user is administratively restrictedRefund creation serialized with SELECT FOR UPDATE and single open refund enforcement
20ae3337by Andrew Camilleri (Kukks)+1310−41655 files
This commit removes a per-invoice checkout language option and translates more public-facing text so it can be localized. It is a feature-cleanup and internationalization change, not a security fix. There is no evidence of a vulnerability …
This commit fixes a bug where BTCPay Server's Point of Sale and Crowdfund inventory counts could become wrong after unpaid or expired invoices. Previously, the system could add inventory back multiple times for the same invoice, making it …
Business-logic flaw: inventory counts could be inflated by duplicate restocking eventsState-machine fix: previous status now tracked to prevent double-countingRace/ordering concern mitigated by deterministic event-barrier for tests
This commit fixes a bug in BTCPay Server where marking an already-expired invoice as 'invalid' could cause the app inventory to be restocked twice. The fix tracks each invoice's previous status during status transitions and skips the inven…
Business-logic bug causing duplicate inventory restockingStatus-transition event missing prior-state contextInventory manipulation possible through invoice state changes
This commit adds a new store-level setting that lets merchants choose which language customers see on public pages such as invoices, payment requests, and pull payments. It also marks more text on those pages as translatable. There is no d…
New per-request language scoping via AsyncLocal with explicit BeginRequest/Restore disposalSignalR hub now applies store language to controller calls that bypass MVC filtersRouteStoreResolver centralizes route-value-to-store-id lookup with 10-minute sliding memory-cache
This commit fixes two bugs in BTCPay Server's wallet transaction API. First, when users filtered transactions by both status (confirmed/unconfirmed) and label, the same transaction could appear twice in the results because the filtering lo…
Fixes duplicate entries in API query results due to incorrect filter compositionReplaces unsafe uint256.Parse with uint256.TryParse to prevent unhandled exceptions on malformed inputAdds server-side input validation returning structured 404 API error for invalid transaction IDs
This commit only updates the version tag of the LND (Lightning Network Daemon) Docker image used in test environments from v0.21.7-beta to v0.21.8-beta. It does not change any production application code, configuration logic, or runtime be…
This commit simply bumps the version numbers of three NuGet packages: a test reporting helper and two FIDO2 authentication libraries. There is no indication in the commit itself that these updates fix a security problem, and no external re…
This commit updates many third-party software libraries (NuGet packages) to newer versions and makes small code adjustments so BTCPay Server stays compatible with those updates. The most notable security-relevant change is a rewrite of the…
Dependency version bumps for libraries with known security maintenance value (HtmlSanitizer, Fido2, MailKit, Microsoft.AspNetCore, System.Security.Cryptography.Pkcs)Manual CSV field escaping added to prevent formula/CSV injection in wallet transaction exportsFido2 configuration/AppID handling changed during Fido2 library upgrade
This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when an API key had permissions tied to more than one store. The fix also corrects how usage counts are recorded and displa…
Fixes a UI crash in an administrative API-key usage pageCorrects aggregation of permission usage records when permissions are scoped to specific storesChanges database upsert to persist full permission string including store scope
This commit fixes a crash in BTCPay Server's admin page that shows how an API key has been used. The crash happened when the same permission (like 'view invoices') was used for more than one store. The fix also corrects how usage counts ar…
Fixes a runtime crash in an administrative API-key usage viewCorrects aggregation of permission usage records that previously could duplicate or conflate store-scoped entriesChanges upsert to persist full permission string including scope, preventing legacy-style policy-only rows from overwriting each other
This commit fixes a math bug in how BTCPay Server rounds very small negative amounts. Previously, a helper called RoundToSignificant divided by the signed value instead of its absolute value, so negative numbers behaved differently from po…
Rounding/truncation bug in financial amount handlingNegative-amount handling asymmetry that could alter displayed or computed balancesFee-bump calculation could fall below Bitcoin incremental relay fee requirement
This commit fixes a crash in the API key authorization page. When a user submits the form without clicking either the 'Authorize' or 'Cancel' button, the server tries to read a missing command value, which could cause an error. The fix saf…
Null dereference in request handling pathUnhandled exception could lead to error disclosure or availability impactDefensive null-safety hardening in controller action
This commit hardens how BTCPay Server downloads translation files from GitHub. It adds checks so the app only fetches files from the project's own trusted GitHub organization, blocks automatic web redirects, and supports a new optional red…
Server-side request forgery (SSRF) protection added: URI host/path validation before outbound fetchAutomatic HTTP redirects disabled for translation update clientManifest redirect field introduced with same-origin/org trust validation
This commit hardens how BTCPay Server downloads translation files from the internet. It adds checks so the server only fetches language packs and manifest redirects from the trusted btcpayserver GitHub organization, turns off automatic HTT…
Server-side request forgery (SSRF) hardening: URI scheme, host, and path prefix are validated before outbound fetchOpen-redirect / HTTP redirect abuse mitigation: AllowAutoRedirect set to false on the translation HttpClientPath traversal mitigation: pack file paths resolved as relative URIs and validated against trusted org prefix
This commit removes old database upgrade scripts (migrations) from before BTCPay Server version 1.12.0 and replaces them with a single consolidated starting schema. It also trims the startup migration task by deleting obsolete data-convers…
Large-scale deletion of database migration historyConsolidation of cumulative schema into a single init SQL scriptRemoval of legacy data-migration logic from startup task
This commit is a large database cleanup: BTCPay Server removed all old EF Core migration files before version 1.12.0 and replaced them with a single consolidated SQL script that creates the current schema from scratch. It also trims the st…
Large schema consolidation could silently drop or alter constraints/indexes compared to the incremental migration historyRemoval of legacy migration executors means installations upgrading from very old versions must rely on the consolidated init script and any remaining IMigrationExecutor implementationsNo explicit security claim or CVE reference in commit message or diff
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
AI review queuedHarden payment accounting and app inputs, and correct POS top-up records (#7772)by Nicolas Dorier · 930bed7d · Oct 29, 2026 · 22 filesMessage 58 · ThinModerate 61Details
Commit message · Nicolas Dorier
Harden payment accounting and app inputs, and correct POS top-up records (#7772)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
This commit is a defensive hardening patch for BTCPay Server. It adds length limits to many user-supplied inputs (email addresses, URLs, order IDs) to prevent oversized or malformed data from causing problems, fixes a currency-conversion calculation so payment accounting uses correct math, and corrects how point-of-sale 'top-up' transactions are recorded so receipts don't show wrong amounts. The changes reduce the risk of denial-of-service, accounting errors, and possibly minor injection issues, but the commit itself does not describe a specific active vulnerability.
AI review queuedIsolate payout RBF regression and preserve failure diagnosticsby Nicolas Dorier · 00989a6c · Oct 29, 2026 · 5 filesMessage 60 · AdequateInformational 22Details
Commit message · Nicolas Dorier
Isolate payout RBF regression and preserve failure diagnostics
60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 22/100
This commit is primarily a regression test and diagnostic improvement for a Bitcoin RBF (Replace-By-Fee) payout bug in BTCPay Server. It adds an automated browser test that verifies pull-payment payouts still complete correctly after a transaction is bumped via RBF. The code changes to the actual application are minimal—just adding CSS class names to form elements so the test can locate them. There is no direct evidence in the commit of an exploitable security vulnerability; it appears to be a fix for a functional regression where RBF-bumped transactions might not be properly tracked as completed payouts.
Security candidateFix wallet address, email credential and invoice policy handling (#7768)by Nicolas Dorier · 7cc69750 · Oct 29, 2026 · 10 filesMessage 58 · ThinModerate 57Details
Commit message · Nicolas Dorier
Fix wallet address, email credential and invoice policy handling (#7768)
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
credential or privilege statesigning or wallet path
AI analysis · Moderate 57/100
This commit fixes several bugs in BTCPay Server. The most notable changes are: (1) email SMTP passwords are now only reused when the mail server hasn't changed, preventing a stored password from being sent to a different server; (2) anonymous BitPay API users can no longer override a store's invoice confirmation-speed policy; and (3) wallet change events are now published when payment methods are added or removed, and cached receive addresses are cleared when a wallet's derivation scheme changes, which helps prevent stale or wrong addresses from being handed out. The commit is described by the vendor as a bug-fix, not a security patch, and no CVE or independent researcher attribution is present in the materials.
Security candidateMerge branch 'fix/sanitize-rich-text-editors'by Nicolas Dorier · 814aaafb · Oct 29, 2026 · 12 filesMessage 45 · ThinHigh 71Details
Commit message · Nicolas Dorier
Merge branch 'fix/sanitize-rich-text-editors'
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationboot or update pathmerge-commit duplicate discount
AI analysis · High 71/100
This commit hardens how BTCPay Server handles rich-text fields (like item descriptions and email bodies). It replaces a client-side editor filter with server-side HTML sanitization, strips out HTML form elements such as <input> and <button>, and removes inline <style> blocks from rich text. These changes reduce the risk that a store owner or attacker could inject malicious HTML that tricks users into unintended actions or leaks information. The patch also expands the list of allowed embedded video/social-media sites and adds unit tests for the new behavior.
Security candidateFix point of sale inventory undercount on multi-unit ordersby Andrew Camilleri (Kukks) · d76427a0 · Oct 28, 2026 · 1 fileMessage 50 · ThinLow 49Details
Commit message · Andrew Camilleri (Kukks)
Fix point of sale inventory undercount on multi-unit orders
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update pathauthentication path
AI analysis · Low 49/100
This commit fixes a bug in BTCPay Server's point-of-sale inventory tracking. When a customer bought multiple units of an item in a single order, the system could mistakenly count the purchase as only one unit sold, causing the inventory count to stay too high. The fix ensures the full shopping cart is used to update inventory instead of a single-item fallback taking over.
Security candidateCap pre-authentication BitPay request body readby Andrew Camilleri (Kukks) · c93be370 · Oct 28, 2026 · 1 fileMessage 50 · ThinModerate 67Details
Commit message · Andrew Camilleri (Kukks)
Cap pre-authentication BitPay request body read
50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Moderate 67/100
This change limits how much data BTCPay Server reads from a BitPay-compatible authentication request before the user is fully authenticated. Previously, the server could read an unbounded amount of request data into memory, which could let an attacker send a huge request body and waste server memory or disk space. The patch caps the body at 1 MB and rejects oversized requests.
Security candidateUpdate NBitcoin and avoid repeated PSBT finalization work (#7765)by Nicolas Dorier · 37bc0693 · Oct 28, 2026 · 4 filesMessage 58 · ThinInformational 23Details
Commit message · Nicolas Dorier
Update NBitcoin and avoid repeated PSBT finalization work (#7765)
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
signing boundarysigning or wallet path
AI analysis · Informational 23/100
This commit updates a Bitcoin library (NBitcoin) to a newer version and simplifies how the app checks whether a transaction proposal (PSBT) is properly finalized. It also tightens access control: if a wallet command is unrecognized, the request is now rejected with a bad-request error instead of falling back to a weaker 'view only' permission. The changes look like routine maintenance plus a small hardening fix, not a clear response to a disclosed security bug.
Security candidateFix LNURL authentication, rate expansion and subscription credit rounding (#7762)by Nicolas Dorier · f4a1b7c7 · Oct 28, 2026 · 13 filesMessage 63 · AdequateModerate 63Details
Commit message · Nicolas Dorier
Fix LNURL authentication, rate expansion and subscription credit rounding (#7762)
63/100 · AdequateMessage clarity
✓ Specific, 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
access controlauthentication path
AI analysis · Moderate 63/100
This commit fixes several unrelated bugs in BTCPay Server. The most security-relevant changes are: (1) LNURL authentication now uses expiring challenges tied to a user's security stamp, preventing old or stale login challenges from being reused; (2) notifications are now filtered by store permission policy, so users without the right role no longer receive sensitive payout/invoice notifications; (3) subscription credit rounding is changed so customers cannot be credited more than they actually paid; and (4) a memory-cache fix prevents lightning address lookups from returning stale null results. The rate-rule change adds a length limit to prevent very large nested rate expressions from being processed.
AI review queuedHarden invoice monitoring, subscription balances and API access (#7761)by Nicolas Dorier · 8e284f21 · Oct 28, 2026 · 20 filesMessage 58 · ThinModerate 61Details
Commit message · Nicolas Dorier
Harden invoice monitoring, subscription balances and API access (#7761)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
This commit is a security hardening patch for BTCPay Server. It adds account lockout to password checks when users change their email or password, closes a JSON deserialization gap that could allow unexpected type information to be processed, limits how large Lightning payout responses can be, prevents subscription balances from growing beyond safe limits, and fixes invoice monitoring so it does not rely on stale invoice data while waiting for payments.
Security candidateFix form permissions, payment updates and onion validation (#7759)by Nicolas Dorier · 3b84c69a · Oct 28, 2026 · 11 filesMessage 58 · ThinModerate 65Details
Commit message · Nicolas Dorier
Fix form permissions, payment updates and onion validation (#7759)
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
credential or privilege state
AI analysis · Moderate 65/100
This commit fixes three separate issues in BTCPay Server: (1) private forms could be submitted by unauthorized users because permission checks were missing, (2) payment updates could trigger errors or incorrect events when multiple payments belonged to the same invoice, and (3) Tor (.onion) address validation was too simple and could be bypassed or misused. It also fixes two JavaScript error messages so they display as plain text instead of HTML, preventing possible cross-site scripting (XSS) when error content is shown to users.
Security candidateFix store isolation and wallet policy enforcement (#7754)by Nicolas Dorier · 0d8b801a · Oct 28, 2026 · 13 filesMessage 58 · ThinModerate 65Details
Commit message · Nicolas Dorier
Fix store isolation and wallet policy enforcement (#7754)
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
signing or wallet pathboot or update path
AI analysis · Moderate 65/100
This commit fixes several authorization and isolation bugs in BTCPay Server. The most important changes prevent a user from seeing other users' store apps, stop non-admins from creating cold wallets when the server policy forbids it, and prevent a malicious store's custom CSS from being loaded in the admin backend. It also fixes a few data-update bugs that could let a request change fields it shouldn't, and a cancellation-token leak.
AI review queuedVarious optimizationsby Nicolas Dorier · 4669eca8 · Oct 28, 2026 · 4 filesMessage 18 · OpaqueInformational 24Details
Commit message · Nicolas Dorier
Various optimizations
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
signing or wallet pathparser or protocol pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 24/100
This commit is titled 'Various optimizations' and makes small code cleanups across four files. The most notable change is in a Razor view where tooltip HTML is now generated more safely: previously, user-controlled text was inserted directly into an HTML attribute without quotes, which could have allowed special characters to break out of the attribute. The other changes are regex performance tweaks and a minor refactoring of derivation scheme parsing. There is no explicit security claim by the project, and no independent researcher is credited.
Security candidateHarden Bitpay compatibility APIby Nicolas Dorier · f3d09d93 · Oct 28, 2026 · 3 filesMessage 35 · OpaqueModerate 61Details
Commit message · Nicolas Dorier
Harden Bitpay compatibility API
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
defensive validationauthentication path
AI analysis · Moderate 61/100
This commit tightens the Bitpay-compatible authentication path in BTCPay Server. Previously, a request authenticated with a valid cryptographic SIN could act as the first token linked to that account, regardless of which token the caller actually supplied. The patch now reads the token from the request and only authorizes the matching token, preventing one token's privileges from being used in place of another's. The commit title says 'Harden' and no explicit security disclosure is provided, so the exact vulnerability is inferred from the code change rather than stated by the vendor.
Security candidateHandle store authorization resourcesby Nicolas Dorier · 814321cb · Oct 28, 2026 · 1 fileMessage 40 · ThinModerate 63Details
Commit message · Nicolas Dorier
Handle store authorization resources
40/100 · ThinMessage clarity
✓ Descriptive subject✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Moderate 63/100
This commit changes how BTCPay Server figures out which store a user is acting on behalf of during permission checks. Previously, when an authorization policy checked a scoped permission, the code only looked at the raw 'resource' object as a plain string. The patch adds a fallback: if the resource is a StoreData object, use that store's ID as the scope. This likely fixes a bug where store-scoped permissions were not being resolved correctly in certain code paths, which could allow a user with permission on one store to perform actions on another store or have their permissions evaluated incorrectly. However, the diff is tiny and partial, so the exact attack path is not visible from this commit alone.
AI review queuedImprove Lightning payout processingby Nicolas Dorier · c5603587 · Oct 28, 2026 · 3 filesMessage 35 · OpaqueModerate 59Details
Commit message · Nicolas Dorier
Improve Lightning payout processing
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 59/100
This commit hardens how BTCPay Server marks Lightning payouts as paid. It adds checks that ensure a payout is still in the expected state and that its payment proof has not unexpectedly changed before the system finalizes it. This reduces the risk of a payout being incorrectly marked as completed—through race conditions, retries, or tampering—while the underlying proof data has changed. The change is defensive and appears aimed at preventing double-payout or state-confusion bugs in automated Lightning withdrawals.
AI review queuedSimplify payout destination handlingby Nicolas Dorier · 983259ad · Oct 28, 2026 · 1 fileMessage 35 · OpaqueLow 25Details
Commit message · Nicolas Dorier
Simplify payout destination handling
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 25/100
This commit simplifies how BTCPay Server builds Bitcoin payment links (BIP21 URLs) when processing payouts. Previously, the code handled two separate cases: one for raw Bitcoin addresses and one for BIP21 URLs (like 'bitcoin:...' links). Now it treats both through a common interface. The change removes special handling that modified existing BIP21 URLs in place, instead always generating a fresh BIP21 URL from the address. This is a code cleanup/refactoring change. There is no direct evidence in the commit that this fixes a security vulnerability, but it removes a code path that could potentially mishandle externally supplied BIP21 URLs.
AI review queuedBound URL template renderingby Nicolas Dorier · 7cbc7b7b · Oct 28, 2026 · 2 filesMessage 35 · OpaqueLow 40Details
Commit message · Nicolas Dorier
Bound URL template rendering
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 40/100
This commit adds a length cap and safer string building to a URL template renderer in BTCPay Server. Before the change, an attacker or user who controlled template variables could cause the server to build extremely long strings, potentially wasting memory or CPU. The patch limits URL output to 8,192 characters and returns an empty string if the bound is exceeded. It appears to be a hardening fix rather than a response to a disclosed vulnerability.
AI review queuedMerge pull request #7750 from btcpayserver/fix/vue-stored-template-xssby Nicolas Dorier · 15376c82 · Oct 28, 2026 · 4 filesMessage 58 · ThinHigh 75Details
Commit message · Nicolas Dorier
Merge pull request #7750 from btcpayserver/fix/vue-stored-template-xss
Keep stored text out of Vue templates
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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · High 75/100
This merge commit appears to fix a stored cross-site scripting (XSS) issue in BTCPay Server's Vue.js templates. The changes prevent user-controlled text (wallet labels, form configuration JSON, and validation output) from being processed by Vue, which could otherwise allow an attacker to inject malicious JavaScript that runs in another user's browser. The patch uses the `v-pre` directive to tell Vue to skip certain HTML elements, and moves form configuration data out of a Vue-bound textarea into a plain JavaScript variable.
AI review queuedKeep stored text out of Vue templatesby Nicolas Dorier · 5e855fbb · Oct 28, 2026 · 4 filesMessage 45 · ThinModerate 63Details
Commit message · Nicolas Dorier
Keep stored text out of Vue templates
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 63/100
This commit changes how BTCPay Server handles text that is stored in web pages and later used by Vue.js. It adds 'v-pre' markers to tell Vue to leave certain pieces of text alone, and it stops reading a form's JSON configuration directly from a textarea that Vue also controls. The likely goal is to prevent Vue from accidentally treating stored data as a template, which could lead to script injection or data leakage if an attacker can control that stored text. However, the patch is small and does not by itself prove an exploitable vulnerability exists.
Security candidateSeparate password lockouts from account restrictionsby Nicolas Dorier · f7b8f4cf · Oct 27, 2026 · 19 filesMessage 50 · ThinModerate 61Details
Commit message · Nicolas Dorier
Separate password lockouts from account restrictions
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Moderate 61/100
This commit rewrites how BTCPay Server blocks users. Previously, the app reused ASP.NET Identity's password-lockout mechanism to disable accounts permanently (for admin bans) and for subscription/monetization reasons. That caused a side effect: too many wrong password attempts could lock an account and also disable its API keys. The change introduces a separate 'user access restrictions' table so that password lockouts and account disabling are independent. API keys now keep working during a temporary password lockout, while admin or monetization restrictions still block access. The commit also adds a migration that converts existing permanent lockouts into the new restriction records.
Security candidateRespect rejected API key permissions (#7744)by Nicolas Dorier · 629a0f48 · Oct 27, 2026 · 2 filesMessage 53 · ThinModerate 62Details
Commit message · Nicolas Dorier
Respect rejected API key permissions (#7744)
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
credential or privilege state
AI analysis · Moderate 62/100
This commit fixes a bug in BTCPay Server's API key authorization flow. When a user was asked to approve a set of permissions for an app, unchecking (rejecting) certain permissions was being ignored. As a result, the issued API key could end up with permissions the user explicitly rejected. The fix ensures rejected permissions are not granted and that the system correctly asks again later if an app requests a previously rejected permission.
Security candidateMerge pull request #7743 from NicolasDorier/harden-json-parsingby Nicolas Dorier · 6ab61a90 · Oct 27, 2026 · 48 filesMessage 73 · AdequateModerate 63Details
Commit message · Nicolas Dorier
Merge pull request #7743 from NicolasDorier/harden-json-parsing
Harden JSON parsing against date coercion and excessive nesting
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
defensive validationcryptography-sensitive pathsigning or wallet pathparser or protocol pathmerge-commit duplicate discount
AI analysis · Moderate 63/100
This commit replaces many direct JSON parsing calls across BTCPay Server with a new, stricter helper called JsonParser. The helper prevents two specific problems: it no longer turns strings that look like dates into real date values automatically, and it limits how deeply nested JSON structures can be. These changes reduce the risk that an attacker could craft unusual JSON data that causes the server to misinterpret values or crash during processing. The commit also adds a test showing that deeply nested and date-like strings are handled safely.
Security candidateHarden JSON parsingby Nicolas Dorier · 9aac2c81 · Oct 27, 2026 · 48 filesMessage 28 · OpaqueModerate 63Details
Commit message · Nicolas Dorier
Harden JSON parsing
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
defensive validationcryptography-sensitive pathsigning or wallet pathparser or protocol path
AI analysis · Moderate 63/100
This commit replaces many uses of the standard Newtonsoft JSON parser with a new, stricter 'JsonParser' helper across the BTCPay Server codebase. The new parser prevents date-looking strings from being silently turned into real dates, rejects JSON that contains extra trailing content, and limits how deeply nested JSON can be. These changes are defensive hardening: they reduce the chance that stored data changes its meaning after being saved and reloaded, and they block unusually deep JSON that could be used to exhaust server resources. The commit does not by itself fix a specific, known exploit, but it closes several risky parsing behaviors.
AI review queuedfix typo (#7569)by Lev Kulieshov · b684e3c0 · Oct 27, 2026 · 2 filesMessage 36 · OpaqueInformational 15Details
Commit message · Lev Kulieshov
fix typo (#7569)
36/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit fixes a simple spelling mistake in a method name: 'GetDiredivationSchemeSettings' was renamed to 'GetDerivationSchemeSettings' in two controller files and the model file that defines it. All call sites were updated consistently, so the code's behavior is unchanged. There is no security issue here.
AI review queuedStabilize flaky Playwright tests (#7739)by Nicolas Dorier · 35ee13a0 · Oct 27, 2026 · 3 filesMessage 63 · AdequateInformational 15Details
Commit message · Nicolas Dorier
Stabilize flaky Playwright tests (#7739)
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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adjusts automated test code to make flaky Playwright browser tests more reliable. It does not change any production code, user-facing behavior, or security mechanisms.