BT
← All projectsBTCPay Server

BTCPay Server

Free, open-source, self-hosted Bitcoin payment processor supporting on-chain and Lightning payments.

BitcoinLightning NetworkPayment infrastructureNormal
Repository coverage

977 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

125security candidates288second-pass queue413AI analyses
168commits · 30 days
317commits · 60 days
557commits · 180 days
897commits · 365 days
Backfill bands
Aug 8 → Feb 9247 seen22 candidatesComplete
Feb 9 → Jun 9197 seen39 candidatesComplete
Jun 9 → Jul 954 seen0 candidatesComplete
Jul 9 → Aug 865 seen16 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

53/100 average clarity
90Strong · 80–100
213Adequate · 60–79
480Thin · 40–59
194Opaque · 0–39
10security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Nicolas Dorier676793111048
Cerberus622290
Andrew Camilleri (Kukks)2233148
Andrew Camilleri1325160
ndeet111133
Chukwuleta Tobechi33714066
rockstardev33612049
Abhijay Jain26610087
thgO.O32512066
dstrukt726061
Tim522074
tumutech222067
Analysis record

Published AI watches

Last scanned 1 minute ago

Informational 15 AI analysisMessage 18 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Rename attribute

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.

5854d8a3by Nicolas Dorier+24−2411 files
No security note in commit
Informational 19 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Use server translations on the invoice checkout page (#7828)

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
bb14f177by Chukwuleta Tobechi+219−585290 files
No security note in commit
Informational 12 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update dependency and .NET 10 servicing images (#7831)

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…

Patch-level .NET runtime/SDK image update (potential servicing fixes, unspecified)Patch-level third-party NuGet package update (CsvHelper 34.0.0 -> 34.1.0, unspecified reason)
d5ecad56by Nicolas Dorier+4−43 files
No security note in commit
High 78 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Harden account and payment handling

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
Vendor flagged security relevance
Informational 19 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Translate remaining public pages and remove invoice checkout language option (#7815)

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 …

1ab0a206by Chukwuleta Tobechi+122−9819 files
No security note in commit
Low 47 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7780 from tumutech/fix-inventory-counts

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
0ba97eacby Nicolas Dorier+187−1611 files
No security note in commit
Low 44 AI analysisMessage 83 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix duplicate inventory returns when expired invoices are marked invalid

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
6d4beac4by tumutech+187−1611 files
No security note in commit
Informational 24 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Apply store’s language on customer-facing pages (#7656)

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
55d71e89by Chukwuleta Tobechi+449−10422 files
No security note in commit
Low 29 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7810 from efeesrefinal/fix/wallet-transaction-filters

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
867209d1by Nicolas Dorier+27−93 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Bump LND to v0.21.8-beta

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…

4bcdc689by r1ckstardev+8−84 files
No security note in commit
Informational 11 AI analysisMessage 35 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update NuGet dependencies

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…

9951be68by AlfredTheBot69+3−32 files
No security note in commit
Low 34 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Update NuGet dependencies and compatibility

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
bef0935cby Alfred+55−4411 files
No security note in commit
Informational 24 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7795 from tumutech/fix-api-key-permission-usage-analysis

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
c9a45b12by Nicolas Dorier+128−484 files
No security note in commit
Informational 22 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix API key View Usage crash with multi-store permission usage

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
0ade56dfby tumutech+128−484 files
No security note in commit
Moderate 51 AI analysisMessage 81 · Strong
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix RoundToSignificant for negative amounts (#7782)

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
6899974aby Amartya Vikram Singh+30−23 files
No security note in commit
Low 49 AI analysisMessage 50 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix missing command in API key authorization

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
0f31ef51by Nicolas Dorier+1−11 file
No security note in commit
Moderate 59 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7610 from TChukwuleta/ft/manifest-redirect-bcp47

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
381ad1f0by Nicolas Dorier+223−393 files
No security note in commit
Moderate 60 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Support translation repository redirects and BCP 47 identifiers

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
896299cdby Chukwuleta Tobechi+223−393 files
Vendor flagged security relevance
Low 29 AI analysisMessage 73 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Merge pull request #7781 from NicolasDorier/cleanup-pre-1.12-migrations

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
9fbfc6c5by Nicolas Dorier+542−275243 files
No security note in commit
Low 34 AI analysisMessage 45 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Remove migrations prior to BTCPay Server 1.12.0

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
57234d0eby Nicolas Dorier+542−275243 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

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.

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.

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.

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
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

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.

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.

AI review queuedFix flaky email testby Nicolas Dorier · 484fe96e · Oct 6, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flaky email test

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit adds a single line to a test file to wait for a web page element to appear before interacting with it. It is a test reliability fix only and does not change any production code, user-facing behavior, or security boundary.

AI review queuedSmall refactoringby Nicolas Dorier · eba60702 · Oct 6, 2026 · 2 filesMessage 18 · OpaqueLow 45Details
Commit message · Nicolas Dorier

Small refactoring

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 · Low 45/100

This commit tweaks how BTCPay Server blocks internal/private network addresses when making outbound connections (an SSRF protection feature). Previously, if any resolved address was private, the whole request was rejected. Now, the code skips private addresses and tries only public ones. If no public address exists, it still rejects the request. The change is described by the author as a small refactoring, but it alters the security behavior slightly: a hostname that resolves to both public and private addresses will now connect to the public address instead of failing outright. The tests were updated only to match the new error message.

AI review queuedRefactor SSRFby Nicolas Dorier · ed51828a · Oct 6, 2026 · 8 filesMessage 18 · OpaqueLow 45Details
Commit message · Nicolas Dorier

Refactor SSRF

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 · Low 45/100

This commit is a code cleanup that changes how BTCPay Server blocks outgoing requests to internal/local network addresses (SSRF protection). It moves the protection logic from a shared service into an extension method used when configuring HTTP clients. The change appears intended to be behavior-preserving, but it removes some unit tests that previously verified the protection works for Bitpay and Webhook clients. Because the patch is only a refactor and no vulnerability is introduced in the diff, this is not a clear security issue on its own, though removing tests reduces future assurance.

AI review queuedFix flaky testby Nicolas Dorier · 9afe7e80 · Oct 5, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Fix flaky test

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This is a one-line change in an automated test file. It makes the test wait for a web page modal to be fully visible before clicking a button, which should make the test less likely to fail randomly. There is no change to production code and no security relevance.

Security candidateAdd dedicated permission and CSRF protection for invoice status changes (#7643)by Nicolas Dorier · 36d4d8b2 · Oct 5, 2026 · 10 filesMessage 58 · ThinHigh 74Details
Commit message · Nicolas Dorier

Add dedicated permission and CSRF protection for invoice status changes (#7643)

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 stateauthentication path
AI analysis · High 74/100

This commit hardens BTCPay Server's invoice status changes. Previously, marking an invoice as settled or invalid required the broad 'modify invoices' permission and the web UI action ignored CSRF protection. The patch adds a dedicated, narrower permission for status changes and requires anti-forgery validation on the web UI endpoint, reducing the risk that a malicious web page or overly permissioned API key can flip invoice states.

Security candidateUpdate Google Cloud credential loadingby Nicolas Dorier · 3f9bcabf · Oct 5, 2026 · 1 fileMessage 45 · ThinInformational 24Details
Commit message · Nicolas Dorier

Update Google Cloud credential loading

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Informational 24/100

This commit changes how BTCPay Server loads Google Cloud service-account credentials. It switches from a general Google credential parser to a more specific service-account credential parser. The change is likely a hardening or compatibility fix, but the commit message gives no security context, so we cannot tell whether it fixes a known vulnerability or is just routine maintenance.

AI review queuedBump dependenciesby Nicolas Dorier · 03c8d8a2 · Oct 5, 2026 · 7 filesMessage 18 · OpaqueLow 29Details
Commit message · Nicolas Dorier

Bump dependencies

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 · Low 29/100

This commit updates many third-party software libraries used by BTCPay Server to newer versions. The changes also adjust how FIDO2/WebAuthn security-key support is configured to match the newer library. Dependency bumps can fix security bugs in those libraries, but the commit message does not say which bugs are being fixed, and the diff itself does not show any direct security patch in BTCPay Server's own code.

Security candidateClarify legacy access token permission (#7631)by Nicolas Dorier · 1eee51a3 · Oct 4, 2026 · 12 filesMessage 53 · ThinLow 28Details
Commit message · Nicolas Dorier

Clarify legacy access token permission (#7631)

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 · Low 28/100

This commit renames a permission that controls who can manage old-style BitPay-compatible access tokens. The old name, 'Manage access tokens,' sounded like it applied to modern API keys, but it only ever applied to legacy BitPay tokens. The new name, 'Manage legacy access tokens,' makes that clear. The change is mostly a labeling and code-organization cleanup; it does not appear to add or remove any actual security checks, but it may reduce confusion that could lead to users granting more access than intended.

AI review queuedImprove internal network detectionby Nicolas Dorier · e3e29dc0 · Oct 4, 2026 · 2 filesMessage 35 · OpaqueModerate 63Details
Commit message · Nicolas Dorier

Improve internal network detection

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 63/100

This commit rewrites how BTCPay Server decides whether a network address is 'internal' versus 'public'. The old check only recognized a few private ranges (local loopback and RFC1918). The new check recognizes many more special-use ranges, such as carrier-grade NAT, link-local, documentation/test IPs, multicast, and IPv6 equivalents. The change is framed as a hardening improvement, but the commit message does not explicitly call it a security fix. If the old code was used to block or restrict access to internal services, the previous gaps could have let an attacker trick the server into treating an internal address as public, potentially enabling Server-Side Request Forgery (SSRF) or similar attacks. However, the diff alone does not show a specific vulnerable call site or exploit path.

AI review queuedAdd 2.4.5 changelogby Nicolas Dorier · 0cb14ec7 · Oct 2, 2026 · 1 fileMessage 38 · OpaqueHigh 79Details
Commit message · Nicolas Dorier

Add 2.4.5 changelog

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · High 79/100

This commit only adds a changelog entry for BTCPay Server version 2.4.5. The changelog itself describes several security-related fixes and one breaking change that blocks private-network outbound requests by default to prevent server-side request forgery (SSRF). It also mentions fixes for invoice search scoping, antiforgery validation, payout scoping, refund permissions, and URL validation. Because the commit is just documentation summarizing prior changes, the direct code risk is low, but the listed changes indicate that the 2.4.5 release addresses multiple security issues.

AI review queuedDummy commitby Nicolas Dorier · 8bb7d8ee · Oct 2, 2026 · 1 fileMessage 18 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Dummy commit

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 only reformats code and adds blank lines in a single controller file. No behavior, logic, or security checks were changed. It is a non-functional 'dummy' style/refactoring commit with no security relevance.

AI review queuedBump BTCPayServer.Lightning librariesby Nicolas Dorier · a92e8f9e · Oct 2, 2026 · 2 filesMessage 35 · OpaqueInformational 4Details
Commit message · Nicolas Dorier

Bump 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 4/100

This commit only updates two internal library version numbers (BTCPayServer.Lightning.Common from 1.7.2 to 1.7.3 and BTCPayServer.Lightning.All from 1.7.10 to 1.7.11). No code changes are included, and the commit message does not mention any security fix. Without knowing what changed in those external libraries, this diff alone does not show any security issue or fix.

AI review queuedBump version and dependenciesby Nicolas Dorier · 415625c1 · Oct 1, 2026 · 9 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Bump version and dependencies

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a routine version bump for the BTCPay Server application and updates several third-party software libraries and build tools to newer patch versions. There is no indication in the commit itself that this is a security fix, and no security-relevant code changes are present.

AI review queuedUpdate translation stringsby Nicolas Dorier · fbcfbc8e · Oct 1, 2026 · 2 filesMessage 35 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Update translation strings

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit only updates translation strings in a localization file and removes a trailing newline from a Swagger JSON file. There are no code behavior changes, no security fixes, and no functional modifications.

Security candidateMerge pull request #7612 from minmoto/okjodom/store-credentials-permissionby Nicolas Dorier · a0319215 · Oct 1, 2026 · 10 filesMessage 73 · AdequateModerate 51Details
Commit message · Nicolas Dorier

Merge pull request #7612 from minmoto/okjodom/store-credentials-permission

Add store permission for managing access tokens

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
credential or privilege statemerge-commit duplicate discount
AI analysis · Moderate 51/100

This change introduces a new, more specific permission called 'Manage access tokens' for store-level access token operations in BTCPay Server. Previously, viewing tokens required the broad 'View store settings' permission and creating or revoking tokens required the even broader 'Modify store settings' permission. The patch narrows those checks so that token management now uses its own dedicated permission. The new permission is automatically granted to the built-in 'Manager' role, and it is included by the existing 'Modify store settings' permission, so users who already had full store control keep the same access. This is a security hardening change that reduces the risk of lower-privileged users (for example, guests or employees) being able to create or revoke API access tokens if they had been accidentally given overly broad store settings rights.

Security candidateAdd store permission for managing access tokensby okjodom · 0ea1d8de · Sep 30, 2026 · 10 filesMessage 68 · AdequateModerate 51Details
Commit message · okjodom

Add store permission for managing access tokens

Introduce btcpay.store.canmanagestorecredentials, included by
btcpay.store.canmodifystoresettings and granted to the built-in Manager
role. Store access tokens, pairing, and their navigation now require it,
so roles such as Guest no longer see or manage a store's access tokens.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
credential or privilege state
AI analysis · Moderate 51/100

This change adds a new, more specific permission for managing store access tokens in BTCPay Server. Previously, viewing or managing these tokens required only broad 'view store settings' or 'modify store settings' permissions, which meant lower-privileged roles like Guest could see or manage them. Now, a dedicated 'manage store credentials' permission is required, and it is automatically granted to the built-in Manager role. This is a hardening fix that reduces the risk of privilege misuse, but it is not a patch for a known active exploit.

AI review queuedSimplify plugin database contexts (#7611)by Nicolas Dorier · ae3abbb0 · Sep 30, 2026 · 9 filesMessage 53 · ThinInformational 18Details
Commit message · Nicolas Dorier

Simplify plugin database contexts (#7611)

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 pathparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit is a code cleanup and developer-experience improvement for how BTCPay Server plugins manage their PostgreSQL databases. It introduces a shared helper and base class so plugin authors no longer need to manually wire up database connections, retry logic, and migration history tables. There is no obvious security bug introduced, but any change to database setup code can affect reliability and migration behavior, so it warrants a careful look rather than being dismissed as purely cosmetic.

AI review queuedAdd maintainer docby Nicolas Dorier · 69c44f1e · Sep 29, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Add maintainer doc

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
documentation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit adds a single sentence to an internal maintainer documentation file, instructing maintainers to also update a separate documentation repository when changing documentation structure. It does not modify any code, configuration, or security policy.