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 51 minutes 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 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.

Security candidateFix Basic auth passwords containing colonsby Nicolas Dorier · 5e9d4c4a · Oct 26, 2026 · 2 filesMessage 50 · ThinLow 47Details
Commit message · Nicolas Dorier

Fix Basic auth passwords containing colons

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Low 47/100

This commit fixes a bug in BTCPay Server's Basic authentication handling. Previously, if a user's password contained a colon character (like 'Kitten0@:with:colons'), the system would split the username:password string at every colon and only use the part before the second colon as the password. This meant users with colons in their passwords could not log in properly through the Greenfield API's Basic auth. The fix now splits only on the first colon, treating everything after it as the password.

AI review queuedImprove QRby Nicolas Dorier · 5e974996 · Oct 26, 2026 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Improve QR

0/100 · OpaqueMessage clarity
! Very short subject! 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 makes minor cosmetic and code-formatting changes to the QR code display modal. It adds a little more padding around QR codes, removes some blank lines, and cleans up whitespace in JavaScript. There is no indication of any security fix or behavior change.

Security candidateHandle missing API key command permissionsby Nicolas Dorier · 26920fac · Oct 26, 2026 · 3 filesMessage 45 · ThinLow 44Details
Commit message · Nicolas Dorier

Handle missing API key command permissions

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

This commit fixes a bug in BTCPay Server's API key management page. Previously, if a user removed a permission checkbox from the form and then clicked a related command button, the server would crash with an error because it assumed the permission was always present. The fix checks whether the permission is missing and returns a clean 'Bad Request' error instead of crashing.

AI review queuedUpdate translationsby Nicolas Dorier · 2a60b149 · Oct 25, 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
Why it was queued
translation-only discountsecond-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a routine update to the application's translation string dictionary. It adds, removes, and rewords English UI labels (for example, adding labels like 'Assembly load', 'Attribution', 'BTCPay Server version', and removing older labels like 'All Directions' and 'Email Notifications'). There is no code logic change, no security fix, and no behavior change in the software itself.

AI review queuedUpdate CI actionsby Nicolas Dorier · 191a5920 · Oct 25, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Nicolas Dorier

Update CI actions

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 only updates the versions of some GitHub Actions used in the project's automated testing pipeline. It does not change any application code that users interact with, and there is no indication it fixes or introduces a security issue.

AI review queuedAdd 2.4.6 changelogby Nicolas Dorier · 63b05b94 · Oct 25, 2026 · 1 fileMessage 38 · OpaqueHigh 83Details
Commit message · Nicolas Dorier

Add 2.4.6 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 83/100

This commit is just a changelog entry for BTCPay Server version 2.4.6. The changelog describes the release as a security update that fixes a .NET Brotli decoder vulnerability, distrusts certificates from a compromised certificate authority, and hardens API permissions, generated links, browser actions, subscriptions, redirect URLs, and HTML sanitization. It also thanks three independent security researchers for responsibly disclosing issues. The actual code fixes are not shown in this commit, only the release notes.

AI review queuedBump version and dependenciesby Nicolas Dorier · aa5b9a2c · Oct 25, 2026 · 3 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 it depends on. There is no indication in the commit itself that this is a security fix, and the changes are limited to version numbers in project files. The updated libraries may contain their own fixes, but this commit does not show any direct security-relevant code change.

AI review queuedTighten HTML sanitizer defaults (#7726)by Nicolas Dorier · 14b85737 · Oct 24, 2026 · 23 filesMessage 53 · ThinModerate 66Details
Commit message · Nicolas Dorier

Tighten HTML sanitizer defaults (#7726)

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 validationsecond-pass: unusually broad change
AI analysis · Moderate 66/100

This commit tightens the HTML sanitizer used in BTCPay Server. It splits the previous single sanitizer into a stricter default one and a separate 'rich text' sanitizer for user-provided descriptions. The rich-text sanitizer now restricts CSS, strips dangerous iframe attributes, only allows same-origin iframe behavior for a small list of trusted video hosts, and blocks things like background-image tracking pixels and arbitrary iframe permissions. Several public pages that render user-provided descriptions are switched to the new rich-text sanitizer. The commit also updates the bundled Summernote rich-text editor from version 0.8.18 to 0.9.1.

Security candidateValidate API key authorization redirects (#7721)by Nicolas Dorier · 68bd3424 · Oct 23, 2026 · 2 filesMessage 58 · ThinModerate 67Details
Commit message · Nicolas Dorier

Validate API key authorization redirects (#7721)

58/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
access controldefensive validation
AI analysis · Moderate 67/100

This commit tightens how BTCPay Server validates the web address users are sent back to after authorizing an API key. Previously, the code only rejected non-absolute redirect URLs in one place and did not re-check the redirect after form submission. The new helper requires the redirect to be an absolute http:// or https:// URL and applies the same check in both the GET and POST authorization handlers. This prevents an attacker from tricking the server into redirecting a user to a malicious address or local service after authorization.

Security candidateKeep shared input limits in syncby Nicolas Dorier · 564d9d0a · Oct 22, 2026 · 27 filesMessage 45 · ThinLow 35Details
Commit message · Nicolas Dorier

Keep shared input limits in sync

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Low 35/100

This commit is a code-quality refactor that moves hard-coded length limits into shared constants so all parts of the app enforce the same limits. It does not add new security checks or remove existing ones, but it fixes places where limits were inconsistent (for example, app names allowed 50 characters in one place and 100 in another). Keeping limits in sync reduces the chance that an attacker could bypass a validation rule by using a different API or UI path.

AI review queuedPreserve unresolved template expressionsby Nicolas Dorier · e0bfaa54 · Oct 22, 2026 · 8 filesMessage 35 · OpaqueLow 35Details
Commit message · Nicolas Dorier

Preserve unresolved template expressions

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

This commit changes how BTCPay Server fills in template placeholders (like {OrderId} or {InvoiceId}) in URLs, payment descriptions, and point-of-sale button text. Previously, if a placeholder could not be resolved or had a syntax error, it was replaced with a visible error string such as [NotFound(...)] and could also be URL-encoded, making it unreadable. The new behavior preserves the original placeholder expression unchanged when it cannot be resolved, and adds a dedicated URL template helper that properly encodes resolved values while leaving unresolved placeholders intact. The change is described as a fix/polish rather than a security patch, but it reduces the risk of broken or misleading URLs and user-facing strings.

Security candidateMerge pull request #7713 from btcpayserver/security/seed-signing-pending-idby Nicolas Dorier · c8b0876a · Oct 22, 2026 · 4 filesMessage 78 · AdequateModerate 55Details
Commit message · Nicolas Dorier

Merge pull request #7713 from btcpayserver/security/seed-signing-pending-id

Require transaction review for linked seed signing

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 55/100

This commit changes how BTCPay Server handles signing cryptocurrency transactions with a stored wallet seed. Previously, a user could be sent straight to the seed-signing screen carrying a pre-loaded transaction (a 'pending transaction' and original PSBT). The patch forces that screen to drop any pre-loaded transaction data, so the user must review the transaction before signing. In short, it removes a path that could let an attacker trick someone into signing a transaction they never saw. The rest of the changes are just test and UI tweaks for the Pay Button feature and are not security-related.

AI review queuedUse TextTemplate for placeholder renderingby Nicolas Dorier · cc4adca4 · Oct 22, 2026 · 8 filesMessage 25 · OpaqueLow 45Details
Commit message · Nicolas Dorier

Use TextTemplate for placeholder rendering

25/100 · OpaqueMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body! Contains work-in-progress language
Why it was queued
second-pass: opaque commit message
AI analysis · Low 45/100

This commit replaces several hand-written string-replacement routines with a shared TextTemplate engine for rendering placeholders in URLs, emails, Lightning payment descriptions, and point-of-sale button text. The change is a defensive refactoring: it centralizes how user-supplied values are substituted into templates, making it easier to ensure values are encoded consistently. The new test shows that URL placeholders are now URL-encoded, which reduces the risk of malicious values breaking or manipulating generated links. There is no direct evidence in the commit of an exploitable vulnerability being fixed, but the change removes a common source of injection and encoding mistakes.

Security candidateReject workflow state from seed signing linksby Nicolas Dorier · f3481aa5 · Oct 22, 2026 · 4 filesMessage 45 · ThinModerate 57Details
Commit message · Nicolas Dorier

Reject workflow state from seed signing links

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 57/100

This commit changes how BTCPay Server handles wallet signing links that use a stored seed. Previously, clicking a 'seed' signing link could automatically carry over a pending transaction and original PSBT (a partially-signed Bitcoin transaction) from the user's workflow state. The patch makes the seed signing page discard that workflow state and only accept signing context supplied directly in the link. This likely closes a security issue where a malicious or crafted link could trick a user into signing a different transaction than expected by reusing state from a previous session.

AI review queuedMerge pull request #7711 from comwanga/fix/fast-test-ci-discovery-7710by Nicolas Dorier · 419f96ca · Oct 21, 2026 · 4 filesMessage 83 · StrongInformational 15Details
Commit message · Nicolas Dorier

Merge pull request #7711 from comwanga/fix/fast-test-ci-discovery-7710

test: restore CI coverage for FastTest-tagged tests

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only changes test labels from 'FastTest' to 'Fast' in four test files. It restores which automated tests run in the project's fast/CI test suite. There is no change to production code, user-facing behavior, or security functionality.

AI review queuedtest: restore CI coverage for seven fast testsby comwanga · 4edd34e7 · Oct 21, 2026 · 4 filesMessage 67 · AdequateInformational 15Details
Commit message · comwanga

test: restore CI coverage for seven fast tests

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only renames test category labels from 'FastTest' to 'Fast' in seven automated tests. It does not change any production code, user-facing behavior, or security logic. The change is purely to restore these tests running in the project's continuous integration (CI) pipeline.

AI review queuedRequire POST for logoutby Nicolas Dorier · 0747c704 · Oct 20, 2026 · 6 filesMessage 28 · OpaqueModerate 52Details
Commit message · Nicolas Dorier

Require POST for logout

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Moderate 52/100

This change makes the logout action require a POST request instead of a simple link click (GET). The old GET-based logout could potentially be triggered by a malicious web page tricking a logged-in user's browser into visiting the /logout URL, logging them out unexpectedly. By switching to a POST form button, the logout can no longer be triggered by a simple embedded link or image, which is a standard defense against cross-site request forgery (CSRF)-style logout attacks. The patch also updates tests and navigation UI to use the new POST form.

AI review queuedHarden public form valuesby Nicolas Dorier · aad2f3bc · Oct 20, 2026 · 8 filesMessage 35 · OpaqueHigh 77Details
Commit message · Nicolas Dorier

Harden public form values

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
defensive validationsecond-pass: opaque commit message
AI analysis · High 77/100

This commit hardens how BTCPay Server handles public web forms used during checkout, such as crowdfunding and point-of-sale purchases. Before the fix, shoppers could tamper with hidden or visible form fields to change prices, add bogus fees, inject oversized data, or overwrite server-only values. The patch now forces the real price to be set after the user submits the form but before validation, rejects non-numeric amount adjustments, clears values that should be server-controlled, caps text field lengths at 10,000 characters, and adds tests showing these tampering attempts are now blocked.

Security candidateHarden wallet error handling and PSBT input (#7701)by Andrew Camilleri · 717ff11d · Oct 20, 2026 · 3 filesMessage 58 · ThinModerate 51Details
Commit message · Andrew Camilleri

Harden wallet error handling and PSBT input (#7701)

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 boundarydefensive validationsigning or wallet path
AI analysis · Moderate 51/100

This commit tightens up how BTCPay Server handles user-supplied PSBT (Bitcoin transaction) data. It adds a size limit check for PSBTs pasted as text (previously only file uploads were checked) and stops including the raw error message from a failed payjoin receiver in the user-facing error. These changes reduce the risk of oversized input causing resource problems and prevent a malicious or misbehaving payjoin receiver from injecting text into the server's error pages.

AI review queuedBound profile and wallet object fields (#7693)by Andrew Camilleri · 4fa9a330 · Oct 19, 2026 · 3 filesMessage 68 · AdequateLow 44Details
Commit message · Andrew Camilleri

Bound profile and wallet object fields (#7693)

* Bound profile and wallet object fields

* Close profile and wallet validation gaps

68/100 · AdequateMessage clarity
✓ 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 pathsecond-pass: security-sensitive path
AI analysis · Low 44/100

This commit adds input-length and type checks for user profile fields (name and avatar URL) and for transaction comments on wallet objects. Before the change, an attacker could supply oversized names or image URLs, or store very large or wrongly-typed transaction comments, through the Greenfield API. The patch rejects values that exceed set limits and ensures transaction comments are strings, which reduces the risk of database bloat, denial-of-service, and unexpected behavior when the data is later displayed.

Security candidateEnforce API key permission scope (#7684)by Andrew Camilleri · 1348bd05 · Oct 19, 2026 · 3 filesMessage 53 · ThinHigh 77Details
Commit message · Andrew Camilleri

Enforce API key permission scope (#7684)

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

This commit fixes a permission-handling bug in BTCPay Server's Greenfield API. Previously, an API key that was only supposed to manage a single store could be used to create or request broader, server-wide permissions it did not actually have. The change now checks every requested permission against what the current key is allowed to grant, and it also tightens how store-scoped permissions are matched during authorization. In short, it stops a limited key from being upgraded into a more powerful one.

Security candidateFix LNURL URI QR code casingby Nicolas Dorier · c5041bdb · Oct 19, 2026 · 5 filesMessage 45 · ThinLow 25Details
Commit message · Nicolas Dorier

Fix LNURL URI QR code casing

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 25/100

This commit fixes how QR codes are generated for LNURL (a way to pay or log in via Bitcoin Lightning). Previously, non-Bech32 URI-style LNURLs were being converted to ALL UPPERCASE for QR codes, which can break some QR readers and wallet apps because the 'lightning:' prefix should stay lowercase. The change makes QR codes keep the correct casing depending on the LNURL format, reducing the chance that a customer or user can't scan or pay.

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.