What changed, and why it matters
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.
Treat BTCPay Server 2.4.6 as a security update and upgrade from 2.4.5 or earlier. Review the individual pull requests referenced in the changelog (especially #7658-#7729, #7684, #7704, #7714, #7721, #7729) for detailed fix information and assess whether any mitigations are needed before patching.
Security signals we found
Vendor explicitly recommends updating for security reasons
References a CVE (CVE-2026-111497) and a CA compromise
Multiple security-hardening pull requests listed
Independent researchers credited for responsible disclosure
Covers API permissions, authentication, redirect validation, subscriptions, HTML sanitization, and untrusted input
Evidence from the diff
The commit adds a Changelog.md entry for BTCPay Server 2.4.6. It references CVE-2026-111497 (Brotli decoder vulnerability in .NET) and the eMudhra CA key compromise, and lists numerous security-hardening PRs (#7658 through #7729) covering API key scoping, store permissions, logout CSRF protection, redirect URL validation, subscription/account takeover fixes, Payjoin/external URL hardening, and HTML/CSS sanitization. The commit itself contains no source-code changes, so the specific technical details of each fix must be inferred from the referenced PRs, which are not supplied.
Changed components
BTCPay Server 2.4.6 release.NET runtime / Brotli decoderUbuntu container trust store / certificate validationGreenfield API / API keysAuthentication / logout / basic authSubscriptions / account takeoverRedirect URL handlingPublic forms / Crowdfund / Point of Sale / Payment RequestPlugins / Lightning payouts / LNURLCustom HTML/CSS sanitizationInspect captured patch +43 / −0
### Changelog.md
@@ -1,5 +1,48 @@
# Changelog
+**Updating to 2.4.6 is recommended because it addresses the Brotli decoder vulnerability and the eMudhra CA key compromise.**
+
+## 2.4.6
+
+This release includes broad security hardening for API permissions, untrusted input, generated links, and browser actions.
+
+### Breaking changes
+
+* **Invoice email notifications**: Remove the legacy per-invoice `notificationEmail` option; use merchant-controlled email rules instead (#7672) @NicolasDorier
+
+### New features
+
+* **Maintenance**: Show live output, progress, and failure details while changing domains, restarting services, cleaning Docker images, or updating BTCPay Server (#7720) @NicolasDorier
+* **Plugins**: Show persistent diagnostics for plugins automatically disabled after startup or runtime failures (#7708) @NicolasDorier
+
+### Improvements
+
+* **Wallet**: Clarify transaction filters, import and export actions, responsive layout, and fee-bump actions (#7470) @dstrukt
+* **QR codes**: Add a white margin to improve scanning in dark mode (#7735) @NicolasDorier
+* **Checkout settings**: Show readable payment method names instead of internal IDs (#7676) @Psycarlo
+* **Invoices**: Load recent invoice lists significantly faster on large servers (#7707) @NicolasDorier
+* **Bitcoin fees**: Prefer fee estimates from the connected Bitcoin Core node (#7682) @NicolasDorier
+* **Generated links**: Consistently use the configured public server URL (#7661 #7662 #7663) @NicolasDorier
+
+### Fixes
+
+* **Runtime security**: Update .NET and the Ubuntu container trust store to fix the [Brotli decoder vulnerability (CVE-2026-111497)](https://github.com/dotnet/announcements/issues/494) and distrust certificates affected by the [eMudhra CA key compromise](https://ubuntu.com/blog/emudhra-ca-compromise-fixes-available) @NicolasDorier
+* **API Keys**: Prevent server errors when API key permission forms are incomplete (#7733) @NicolasDorier
+* **Basic authentication**: Allow Greenfield API access when account passwords contain colons (#7736) @NicolasDorier
+* **Public forms**: Keep Crowdfund, Point of Sale, and Payment Request forms on their original route when validation fails (#7716) @NicolasDorier
+* **Lightning payouts**: Complete LNDHub-on-LNbits payouts correctly, retain pending payment proofs when lookups return no result, and round LNURL payouts down to whole satoshis (#7653 #7679 #7703) @NicolasDorier @shin4141
+* **LNURL**: Preserve URI casing in payment and authentication QR codes, and require settled payments during verification (#7681) @NicolasDorier
+* **Email Rules**: Limit rendered messages to 100 recipients and handle empty recipient placeholders without interrupting other rules (#7690 #7718) @Kukks @comwanga
+* **Subscriptions**: Prevent new subscriptions from taking control of existing accounts, protect administrators from subscriber lockouts, and make concurrent credit updates atomic (#7654 #7660 #7700) @NicolasDorier @Kukks
+* **Templates**: Preserve unsupported placeholders in configured URLs, descriptions, and labels (#7717) @NicolasDorier
+* **Security hardening**: Strengthen store permissions, browser actions, external URLs, Payjoin requests, and untrusted input across APIs, wallets, forms, subscriptions, webhooks, and apps (#7658 #7659 #7664 #7665 #7666 #7667 #7669 #7686 #7687 #7688 #7689 #7692 #7693 #7694 #7695 #7696 #7701 #7713 #7722 #7723) @NicolasDorier @Kukks
+* **HTML customization**: Apply stricter sanitization to custom HTML and CSS, while preserving rich media for merchant-authored public app and payment descriptions (#7726) @NicolasDorier
+* **Authentication**: Require protected POST requests for logout; direct links and bookmarks to `/logout` no longer sign users out (#7704) @NicolasDorier
+* **Redirect URLs**: Accept only absolute HTTP or HTTPS redirect URLs in API key authorization and Greenfield or BitPay-compatible invoice requests (#7714 #7721 #7729) @NicolasDorier @tumutech
+* **API Keys**: Keep restricted API keys within their granted store and user permission scope, including when the key owner is a server administrator (#7684) @Kukks
+
+Thanks to @iaohkut, bitcoinbazar21 and Nikhil Agrawal for responsibly disclosing security issues fixed in this release.
+
## 2.4.5
### Breaking changesWhy this scored 83/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.