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-priorityStabilize external Pay Button testby Nicolas Dorier · 8e03e006 · Oct 9, 2026 · 1 fileMessage 55 · ThinTriage 0Details
Commit message · Nicolas Dorier
Stabilize external Pay Button test
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityProtect Payjoin requests from SSRF (#7669)by Nicolas Dorier · 1a43672b · Oct 9, 2026 · 3 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Protect Payjoin requests from SSRF (#7669)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityHarden malformed store, app, and payout data (#7667)by Nicolas Dorier · c76447b5 · Oct 9, 2026 · 10 filesMessage 58 · ThinTriage 8Details
Commit message · Nicolas Dorier
Harden malformed store, app, and payout data (#7667)
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
defensive validation
AI review queuedHarden untrusted HTML and URL handling (#7666)by Nicolas Dorier · cbee1f8c · Oct 8, 2026 · 14 filesMessage 53 · ThinModerate 68Details
Commit message · Nicolas Dorier
Harden untrusted HTML and URL handling (#7666)
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 · Moderate 68/100
This commit tightens how BTCPay Server handles web links and HTML that come from user or invoice data. It blocks dangerous URL schemes like javascript: and data:, and it HTML-encodes values before putting them into emails and web pages. These changes reduce the risk that an attacker could trick an administrator or customer into running malicious code through invoice metadata, subscription redirect URLs, email notifications, or wallet labels.
AI review queuedHarden external input handling (#7665)by Nicolas Dorier · 7ce94b4d · Oct 8, 2026 · 18 filesMessage 53 · ThinModerate 51Details
Commit message · Nicolas Dorier
Harden external input handling (#7665)
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 · Moderate 51/100
This commit adds input validation and safer error handling across BTCPay Server's Greenfield API and web controllers. It prevents negative or nonsensical values for amounts, fees, thresholds, and lightning-address limits; stops malformed JSON error responses from crashing the API client; and makes transaction-label parsing tolerate bad data. Most changes are defensive hardening rather than fixes for known active exploits, but they close paths where an authenticated user or external system could supply dangerous input.
AI review queuedHarden payment and wallet validation (#7664)by Nicolas Dorier · d416854c · Oct 8, 2026 · 10 filesMessage 53 · ThinLow 49Details
Commit message · Nicolas Dorier
Harden payment and wallet validation (#7664)
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 pathparser or protocol pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Low 49/100
This commit fixes several input-validation bugs in BTCPay Server. The most important change corrects a logic error in store settings validation: previously, expiration times were only rejected if they were simultaneously too short AND too long, which effectively allowed any value. The commit also blocks negative or zero amounts for Lightning payments and LNURL invoices, prevents crashes when parsing malformed wallet backup files, and fixes a charting bug for empty wallets. These are hardening fixes rather than a single critical vulnerability.
AI review queuedUse the configured server URL for sensitive links (#7663)by Nicolas Dorier · bc1e4dc3 · Oct 8, 2026 · 12 filesMessage 58 · ThinModerate 59Details
Commit message · Nicolas Dorier
Use the configured server URL for sensitive links (#7663)
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 · Moderate 59/100
This commit changes BTCPay Server so that sensitive links and QR codes use the administrator-configured server URL instead of whatever URL the current request happened to arrive on. Before the fix, if an attacker could get a victim to visit the server through a different domain or path, sensitive links (API key QR codes, login codes, Lightning node config downloads, monetization checkout links, multisig setup invitations, and pending wallet transaction links) could be generated pointing to that attacker-controlled or unexpected URL. The patch makes these features consistently use the canonical server URL configured by the admin, reducing the risk of phishing, session/token leakage, or misdirected actions.
AI review queuedUse canonical URL for generated links (#7662)by Nicolas Dorier · 1db11d9f · Oct 8, 2026 · 6 filesMessage 53 · ThinLow 34Details
Commit message · Nicolas Dorier
Use canonical URL for generated links (#7662)
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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100
This commit changes how BTCPay Server builds links that are shown to users or sent in emails. Instead of using the web address from the current incoming request, it uses a configured canonical server URL. This likely fixes situations where generated links could point to the wrong domain—such as when the server is behind a reverse proxy, accessed via an unexpected hostname, or manipulated by a Host-header attack—preventing users from being redirected to attacker-controlled sites or from email links failing to work.
Lower-priorityInitialize server Base URL on admin login (#7661)by Nicolas Dorier · 768e81dc · Oct 8, 2026 · 5 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Initialize server Base URL on admin login (#7661)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI review queuedRefine wallet transactions toolbar and direction filter (#7470)by dstrukt · dacd885d · Oct 8, 2026 · 4 filesMessage 58 · ThinInformational 15Details
Commit message · dstrukt
Refine wallet transactions toolbar and direction filter (#7470)
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 15/100
This commit is a user-interface polish change for the wallet transactions page. It renames filter labels (for example, 'Outgoing' becomes 'Sent'), reorganizes the toolbar buttons, adds a new icon, and updates tests to match the new labels. There is no security-relevant change.
Lower-priorityPrevent subscriptions from linking to existing accounts (#7660)by Nicolas Dorier · cc0d3022 · Oct 8, 2026 · 3 filesMessage 58 · ThinTriage 0Details
Commit message · Nicolas Dorier
Prevent subscriptions from linking to existing accounts (#7660)
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-priorityRequire settlement in LNURL payment verificationby Nicolas Dorier · 81c9c868 · Oct 8, 2026 · 1 fileMessage 55 · ThinTriage 8Details
Commit message · Nicolas Dorier
Require settlement in LNURL payment verification
55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
defensive validation
Lower-priorityProtect server file deletion from CSRF (#7658)by Nicolas Dorier · 6ea723b7 · Oct 8, 2026 · 2 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Protect server file deletion from CSRF (#7658)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityProtect default role changes from CSRF (#7659)by Nicolas Dorier · 78c0fbaa · Oct 8, 2026 · 3 filesMessage 53 · ThinTriage 0Details
Commit message · Nicolas Dorier
Protect default role changes from CSRF (#7659)
53/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Lower-priorityValidate Pay Button modal messagesby Nicolas Dorier · 9b212182 · Oct 7, 2026 · 2 filesMessage 45 · ThinTriage 8Details
Commit message · Nicolas Dorier
Validate Pay Button modal messages
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validation
Security candidateValidate antiforgery token on app file uploadsby Nicolas Dorier · 7c825f8d · Oct 7, 2026 · 3 filesMessage 45 · ThinModerate 66Details
Commit message · Nicolas Dorier
Validate antiforgery token on app file uploads
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
defensive validationauthentication path
AI analysis · Moderate 66/100
This commit fixes a security gap in BTCPay Server's app file upload feature. Previously, the upload endpoint ignored anti-forgery tokens, which are a standard defense against cross-site request forgery (CSRF) attacks. The patch removes that exemption and updates the JavaScript uploader to include the token with each upload request. A new test verifies the endpoint now requires anti-forgery validation.
Lower-priorityFix payouts made through LNDHub on LNbits remaining stuck in Pendingby Nicolas Dorier · 03129c57 · Oct 6, 2026 · 1 fileMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier
Fix payouts made through LNDHub on LNbits remaining stuck in Pending
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedDocument post release processby Nicolas Dorier · e7e47252 · Oct 6, 2026 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier
Document post release process
35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
This commit only adds documentation describing what maintainers should do after a software release. It does not change any code, configuration, or security behavior of BTCPay Server itself.
Lower-priorityLimit and clean up BitPay pairing codesby Nicolas Dorier · 5d0745ca · Oct 6, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Limit and clean up BitPay pairing codes
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityHide invoice information from public endpoints after one month.by Nicolas Dorier · 94054eef · Oct 6, 2026 · 3 filesMessage 50 · ThinTriage 0Details
Commit message · Nicolas Dorier
Hide invoice information from public endpoints after one month.
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityRemove unused checkout model propertiesby Nicolas Dorier · 10cd9c15 · Oct 6, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Remove unused checkout model properties
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Lower-priorityRemove customer email from checkout modelby Nicolas Dorier · 87d5327a · Oct 6, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Remove customer email from checkout model
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI review queuedBump NBitcoinby Nicolas Dorier · 5ebf8aa1 · Oct 6, 2026 · 3 filesMessage 18 · OpaqueInformational 3Details
Commit message · Nicolas Dorier
Bump NBitcoin
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 3/100
This commit simply updates a third-party library called NBitcoin from version 10.0.14 to 10.0.15 across three project files. There is no description of why the update is being made, no security advisory referenced, and no code changes visible in the commit itself. On its own, this looks like a routine dependency bump with no identifiable security issue.
Lower-priorityRequire approval for employee overpayment refundsby Nicolas Dorier · 5ffb7130 · Oct 6, 2026 · 1 fileMessage 45 · ThinTriage 0Details
Commit message · Nicolas Dorier
Require approval for employee overpayment refunds
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body