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.
Lower-priorityMerge pull request #7751 from btcpayserver/fix/bound-url-template-renderingby Nicolas Dorier · 9a1b8098 · Oct 28, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7751 from btcpayserver/fix/bound-url-template-rendering
Bound URL template rendering
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
merge-commit duplicate discount
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.
Lower-priorityMerge pull request #7749 from btcpayserver/fix/pos-order-line-limitby Nicolas Dorier · da5a7f48 · Oct 28, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7749 from btcpayserver/fix/pos-order-line-limit
Limit point of sale order lines
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
merge-commit duplicate discount
Lower-priorityLimit point of sale order linesby Nicolas Dorier · 121fb903 · Oct 28, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Limit point of sale order lines
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityBind authorized API keys to the selected store (#7748)by Nicolas Dorier · 30ee7381 · Oct 28, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Bind authorized API keys to the selected store (#7748)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityHarden form validation attribute renderingby Nicolas Dorier · dad4998d · Oct 28, 2026 · 5 filesMessage 45 · ThinTriage 8Details
Commit message · Nicolas Dorier
Harden form validation attribute rendering
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validation
Lower-priorityFix subscriber credit balance for the requested currency (#7747)by Tumusiime Francis · 9792e69a · Oct 27, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Tumusiime Francis
Fix subscriber credit balance for the requested currency (#7747)
* fix subscriber credit balance for the requested currency
* fix subscriber credit balance for the requested currency
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
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.
Lower-priorityMerge pull request #7745 from NicolasDorier/validate-lightning-connection-typeby Nicolas Dorier · 7ea4e49f · Oct 27, 2026 · 4 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7745 from NicolasDorier/validate-lightning-connection-type
Validate Lightning connection string type
73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Lower-priorityValidate Lightning connection string typeby Nicolas Dorier · fb31ce3b · Oct 27, 2026 · 4 filesMessage 45 · ThinTriage 8Details
Commit message · Nicolas Dorier
Validate Lightning connection string type
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validation
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.
Lower-priorityMerge pull request #7742 from NicolasDorier/remove-legacy-lightning-parserby Nicolas Dorier · 6eb2cfb3 · Oct 27, 2026 · 4 filesMessage 73 · AdequateTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7742 from NicolasDorier/remove-legacy-lightning-parser
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
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.
Lower-priorityFix subscription credit currency references in OpenAPI (#7737)by Mehmet E. Mayda · MaydaLabs · eab3511f · Oct 27, 2026 · 1 fileMessage 58 · ThinTriage 0Details
Commit message · Mehmet E. Mayda · MaydaLabs
Fix subscription credit currency references in OpenAPI (#7737)
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
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.
Lower-priorityBind development ports to localhostby Nicolas Dorier · b0087450 · Oct 27, 2026 · 4 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Bind development ports to localhost
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityRemove information from changelog to announcementby Nicolas Dorier · a070a162 · Oct 26, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Remove information from changelog to announcement
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedWarn about maintenance command interruptionsby Nicolas Dorier · 1d08f554 · Oct 26, 2026 · 8 filesMessage 45 · ThinInformational 15Details
Commit message · Nicolas Dorier
Warn about maintenance command interruptions
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 · Informational 15/100
This commit only adds a user-facing warning message in the maintenance tool explaining that the server may restart during a command and that the user should refresh the page if disconnected. It also marks several unit tests as 'Fast' tests. There is no security fix or vulnerability change in the code.
Lower-priorityMerge pull request #7738 from NicolasDorier/harden/store-scope-consistencyby Nicolas Dorier · 35e71c1c · Oct 26, 2026 · 2 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Merge pull request #7738 from NicolasDorier/harden/store-scope-consistency
58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body