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 queuedRename attributeby Nicolas Dorier · 5854d8a3 · Nov 20, 2026 · 11 filesMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Rename attribute
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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.
AI review queuedUse server translations on the invoice checkout page (#7828)by Chukwuleta Tobechi · bb14f177 · Nov 19, 2026 · 90 filesMessage 58 · ThinInformational 19Details
Commit message · Chukwuleta Tobechi
Use server translations on the invoice checkout page (#7828)
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
second-pass: unusually broad change
AI analysis · Informational 19/100
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 settings. The visible checkout text is rendered by the server. The change removes the old language selector from the checkout page and deletes many per-language checkout JSON files. It is primarily a feature/refactoring change, not a security fix.
AI review queuedUpdate dependency and .NET 10 servicing images (#7831)by Nicolas Dorier · d5ecad56 · Nov 19, 2026 · 3 filesMessage 73 · AdequateInformational 12Details
Commit message · Nicolas Dorier
Update dependency and .NET 10 servicing images (#7831)
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 12/100
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 a security issue, and the diff itself does not show any code changes that would directly introduce or fix a vulnerability. It is best treated as a normal dependency refresh.
AI review queuedTranslate remaining public pages and remove invoice checkout language option (#7815)by Chukwuleta Tobechi · 1ab0a206 · Nov 17, 2026 · 19 filesMessage 58 · ThinInformational 19Details
Commit message · Chukwuleta Tobechi
Translate remaining public pages and remove invoice checkout language option (#7815)
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 pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
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 being patched.
AI review queuedApply store’s language on customer-facing pages (#7656)by Chukwuleta Tobechi · 55d71e89 · Nov 16, 2026 · 22 filesMessage 58 · ThinInformational 24Details
Commit message · Chukwuleta Tobechi
Apply store’s language on customer-facing pages (#7656)
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
second-pass: unusually broad change
AI analysis · Informational 24/100
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 direct evidence in the commit that this fixes an active security vulnerability; it reads as a feature or hardening change to make customer-facing language selection consistent and to prevent a SignalR hub from bypassing the store-language logic.
AI review queuedMerge pull request #7810 from efeesrefinal/fix/wallet-transaction-filtersby Nicolas Dorier · 867209d1 · Nov 16, 2026 · 3 filesMessage 73 · AdequateLow 29Details
Commit message · Nicolas Dorier
Merge pull request #7810 from efeesrefinal/fix/wallet-transaction-filters
Fix: Wallet transactions listed twice when filtering by status and label
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
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 29/100
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 logic added the transaction once for matching the label and again for matching the status. Second, two API endpoints that look up a single transaction by ID would crash if given an invalid transaction ID instead of returning a proper 'not found' error. The patch corrects the filtering logic and safely handles malformed transaction IDs.
AI review queuedBump LND to v0.21.8-betaby r1ckstardev · 4bcdc689 · Nov 12, 2026 · 4 filesMessage 38 · OpaqueInformational 15Details
Commit message · r1ckstardev
Bump LND to v0.21.8-beta
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
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 behavior of BTCPay Server itself. There is no evidence in the commit or supplied references that this is a security fix or introduces a vulnerability.
AI review queuedUpdate NuGet dependenciesby AlfredTheBot69 · 9951be68 · Nov 11, 2026 · 2 filesMessage 35 · OpaqueInformational 11Details
Commit message · AlfredTheBot69
Update NuGet dependencies
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 11/100
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 references were provided. It looks like a routine dependency maintenance change.
AI review queuedUpdate NuGet dependencies and compatibilityby Alfred · bef0935c · Nov 11, 2026 · 11 filesMessage 45 · ThinLow 34Details
Commit message · Alfred
Update NuGet dependencies and compatibility
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 · Low 34/100
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 wallet transaction CSV export. The new code deliberately prefixes spreadsheet formula characters (like =, +, @) with an apostrophe so that exported CSV files are less likely to trigger malicious formula injection when opened in Excel or similar programs. The commit does not say it is fixing a security bug, and no external advisory is supplied.
AI review queuedFix RoundToSignificant for negative amounts (#7782)by Amartya Vikram Singh · 6899974a · Nov 5, 2026 · 3 filesMessage 81 · StrongModerate 51Details
Commit message · Amartya Vikram Singh
Fix RoundToSignificant for negative amounts (#7782)
The relative error was divided by the signed value, so for a negative amount it was never positive and the first rounding was always accepted. Small negative amounts were rounded to zero (-0.0004 with divisibility 2 became -0.00) instead of keeping their significant digits like positive ones (0.0004 stays 0.0004).
81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 51/100
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 positive ones. Tiny negative amounts could be rounded to zero (for example, -0.0004 became -0.00) while the equivalent positive amount kept its precision. The same patch also makes sure transaction fee bumps are never rounded down below the Bitcoin network's minimum relay-fee increase, preventing a fee-bump transaction from being rejected for paying too little.
AI review queuedMerge pull request #7781 from NicolasDorier/cleanup-pre-1.12-migrationsby Nicolas Dorier · 9fbfc6c5 · Oct 30, 2026 · 43 filesMessage 73 · AdequateLow 29Details
Commit message · Nicolas Dorier
Merge pull request #7781 from NicolasDorier/cleanup-pre-1.12-migrations
Remove migrations prior to BTCPay Server 1.12.0
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
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-conversion helpers. The change is primarily a code-maintenance cleanup. It is not a security patch, but it does carry operational risk: if the consolidated schema does not exactly match what the removed migrations produced, fresh installs or restored databases could behave differently. Several tests that exercised the deleted migrations were also removed or rewritten.
AI review queuedRemove migrations prior to BTCPay Server 1.12.0by Nicolas Dorier · 57234d0e · Oct 30, 2026 · 43 filesMessage 45 · ThinLow 34Details
Commit message · Nicolas Dorier
Remove migrations prior to BTCPay Server 1.12.0
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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 34/100
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 startup migration task, moves a YAML test helper out of production code, and updates related tests. There is no obvious security bug introduced, but any mistake in the consolidated schema could cause data-integrity or upgrade problems for users on older databases.
AI review queuedBump and changelogby Nicolas Dorier · 2868deed · Oct 29, 2026 · 2 filesMessage 28 · OpaqueCritical 100Details
Commit message · Nicolas Dorier
Bump and changelog
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Critical 100/100
This is a version-bump and changelog commit for BTCPay Server 2.4.7. The changelog itself announces that the release fixes 85 security findings reported by Anthropic's OSS Scanner program, including 1 critical and 13 high-severity issues. The actual code changes are only a version number update and the changelog text, but the changelog explicitly describes many security fixes covering payments, invoices, APIs, authentication, Lightning, subscriptions, and more. Because the commit is just packaging the release notes, the security relevance is disclosed by the vendor, and the severity is clearly stated.
AI review queuedUpdate translationsby Nicolas Dorier · ec5429c7 · Oct 29, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Update translations
18/100 · OpaqueMessage clarity
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body
This commit only updates translation strings in a C# resource file. It removes two old English phrases, adds three new ones, and makes no changes to program logic, security checks, or user permissions. There is nothing here that affects security.
AI review queuedHarden view model binding (#7775)by Nicolas Dorier · 947d158e · Oct 29, 2026 · 3 filesMessage 53 · ThinLow 49Details
Commit message · Nicolas Dorier
Harden view model binding (#7775)
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
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Low 49/100
This commit adds [BindNever] attributes to several properties in view models. In ASP.NET Core, [BindNever] tells the framework not to populate those properties from incoming HTTP request data. Without it, an attacker could potentially submit crafted form or query data to overwrite values that the application intended to set internally, such as invoice lists, report results, or transaction lists. This is a hardening change that reduces the attack surface for model-binding abuse, but the commit does not describe a specific vulnerability or exploit.
AI review queuedUpdate BTCPayServer.Lightning librariesby Nicolas Dorier · 397ed0e0 · Oct 29, 2026 · 2 filesMessage 35 · OpaqueInformational 3Details
Commit message · Nicolas Dorier
Update BTCPayServer.Lightning libraries
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 3/100
This commit simply bumps two internal BTCPayServer.Lightning library package versions by one patch release (1.7.4→1.7.5 and 1.7.13→1.7.14). The diff contains no code changes, no security claims, and no disclosed vulnerability details. On its own it is just a routine dependency update.
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.
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.
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.
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.