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.
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.
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.
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.
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.
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.
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.
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.
✓ 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.
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.
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.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controlauthentication path
AI analysis · Informational 15/100
This commit is a large documentation reorganization for BTCPay Server. It moves existing guidance into audience-specific folders (users, operators, developers, maintainers), adds new guides for plugins and API integrations, updates links to point to historical versions of removed docs, and introduces an automated test that checks documentation links and regenerates a configuration reference. There is no code change that affects how BTCPay Server processes payments, stores data, or handles authentication.
Merge pull request #7599 from NicolasDorier/fix/invoice-list-store-permissions
Scope invoice list filters to the current store
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 67/100
This change fixes a permission problem in BTCPay Server's invoice list. Previously, the invoice list page accepted a 'storeid:' search filter or a StoreId parameter that could let a user see invoices from stores they were not supposed to access. The patch forces the invoice list to always use the store ID from the URL route, ignoring any user-supplied store filter, so users can only view invoices for the store they are currently in.
Security candidateContainerize the server settings views into sections (#7501)by dstrukt · 97357e8c · Sep 22, 2026 · 30 filesMessage 58 · ThinInformational 15Details
Commit message · dstrukt
Containerize the server settings views into sections (#7501)
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
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a user-interface redesign, not a security fix. It wraps existing server settings pages into consistent visual sections and adds short explanatory subtitles. No code handling payments, authentication, permissions, or data validation was changed.
✓ Specific, 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 controlboot or update path
AI analysis · Informational 15/100
This commit only updates user-facing help text in the Point of Sale plugin. It replaces outdated guidance about legacy API keys and Basic authentication with newer guidance about API tokens and the correct REST API endpoint. No code logic, authentication checks, or security behavior changed.
This commit refactors how BTCPay Server stores and handles API keys. Previously, the secret API key itself was used as the database primary key, meaning the full secret was stored in plaintext and appeared in URLs/revocation endpoints. Now the system creates a separate public 'key ID' (starting with 'akid_') derived from a hash of the secret, stores only a hash of the secret in the database, and uses the ID for management operations such as revocation. The change also removes the old BitPay 'Basic auth' legacy API key feature entirely. The commit is framed as a security hardening measure, but it is a large refactor rather than a single bug fix.
Security candidateHarden API key storageby Nicolas Dorier · b1294924 · Sep 4, 2026 · 29 filesMessage 28 · OpaqueModerate 60Details
Commit message · Nicolas Dorier
Harden API key storage
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
defensive validationauthentication path
AI analysis · Moderate 60/100
This commit changes how BTCPay Server stores and handles API keys. Previously, the secret API key itself was used as the database primary key and was stored in plaintext. After this change, the database stores a one-way hash of the secret, a short prefix for display, and a separate non-secret ID for management. The actual secret is only kept briefly in memory after creation and is then erased. The commit also removes an old BitPay-compatible 'legacy API key' feature that used Basic authentication with a plaintext key. These are defensive security improvements that reduce the damage if the database is stolen, but they do not by themselves fix an active vulnerability in running code.
fix(plugin-manager): use update lookup for installed plugins (#7536)
70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Low 35/100
This commit changes how BTCPay Server's plugin manager asks the plugin directory for update information. Previously, the server fetched the full catalog of plugins and then filtered locally. Now it sends a list of the plugins actually installed or pending on the local server and asks only for updates to those. This reduces unnecessary data exposure of the server's plugin inventory to the directory and may avoid bugs where pending or disabled plugins were not considered when checking for updates. It is a hardening/fix change rather than a clear-cut security patch, and the commit message does not claim it fixes a vulnerability.
Prevent monetization from overriding administrator account lockout (#7523)
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
access control
AI analysis · Moderate 61/100
This change fixes a bug where BTCPay Server's paid-subscription ('monetization') system could automatically re-enable an administrator account that had been manually disabled. Previously, when a subscription renewed or was bypassed, the monetization service would call SetDisabled(user, false) without knowing why the account was disabled. The patch adds a 'source' trail so monetization can tell whether it was the one that disabled the account, and it now suspends the subscription instead of overriding an admin lockout. In short: admin-imposed account lockouts can no longer be accidentally undone by billing automation.
Security candidateRename CryptoMarket rate provider to Notbank (#7526)by Nicolas Dorier · e1c27379 · Aug 28, 2026 · 6 filesMessage 58 · ThinInformational 19Details
Commit message · Nicolas Dorier
Rename CryptoMarket rate provider to Notbank (#7526)
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
cryptography-sensitive path
AI analysis · Informational 19/100
This commit renames BTCPay Server's exchange-rate source from 'CryptoMarket' to 'Notbank'. It swaps the old provider code for a new one that calls Notbank's API, and adds a database migration that rewrites existing store settings so they continue to use the new rate source name. There is no indication this fixes a security vulnerability; it appears to be a routine rebranding/integration change.
✓ Subject identifies a change✓ Names security-relevant behavior explicitly! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
explicit security languagesigning or wallet pathboot or update pathauthentication pathparser or protocol path
AI analysis · High 78/100
This is a broad security patch for BTCPay Server 2.4.3. It fixes several access-control gaps (for example, lower-privileged store users could manage server admins or see sensitive API keys), hardens user-profile changes by requiring the current password, removes a third-party comment system (Disqus) that could inject scripts, adds rate limits to public invoice creation, stops plugins with known incompatibilities from loading, and tightens validation of Bitcoin transactions and multisig wallet setup. The changelog explicitly calls it a security release and recommends updating for multi-user servers.
Security candidateDisabled unwanted routesby Nicolas Dorier · 6689cad4 · Aug 7, 2026 · 5 filesMessage 28 · OpaqueLow 49Details
Commit message · Nicolas Dorier
Disabled unwanted routes
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
authentication path
AI analysis · Low 49/100
This commit marks several public methods on ASP.NET Core controllers with [NonAction], which prevents them from being exposed as web-accessible HTTP routes. Without this attribute, these helper methods could be reached directly via URL, potentially allowing users to bypass intended workflows, access internal logic, or trigger actions that were only meant to be called by other controller code. The change is a hardening fix rather than a clear-cut exploit patch, because the diff alone does not show that any of these routes were actually reachable or dangerous in practice.
Security candidateDisable Greenfield Basic Auth by default after 5 min of user creation (#7492)by Nicolas Dorier · 61cb0702 · Aug 5, 2026 · 12 filesMessage 63 · AdequateModerate 60Details
Commit message · Nicolas Dorier
Disable Greenfield Basic Auth by default after 5 min of user creation (#7492)
63/100 · AdequateMessage clarity
✓ Specific, 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 controlboot or update pathauthentication path
AI analysis · Moderate 60/100
This change is a hardening measure, not a direct bug fix. BTCPay Server now turns off username/password Basic authentication for its Greenfield API by default once an account is more than five minutes old. Users can re-enable it manually, but the safer default is to require API keys instead. The vendor describes this as a defense-in-depth follow-up to reduce the impact of other authentication bugs.