BTCPay Server Issues Emergency Update 2.4.7 Following Anthropic AI Security Scan
BTCPay Server has released version 2.4.7, fixing one critical, 13 high, 52 medium and 19 low-severity findings. If you run it, especially for more than one merchant, update soon, and read the checklist below first.
On 29 October 2026, the BTCPay Server project released version 2.4.7, an emergency bug-fix update. The release notes say it fixes 85 security findings reported through Anthropic’s OSS Scanner program, along with reliability and payment-accounting problems. The team calls updating “highly recommended,” especially for servers shared by several merchants.
BTCPay Server is a free, open-source, self-hosted tool for accepting Bitcoin payments without a middleman. If you or a merchant you know runs it, this update is for you.
What was fixed
The findings, using the scanner’s own severity ratings:
| Severity | Fixed findings |
|---|---|
| Critical | 1 |
| High | 13 |
| Medium | 52 |
| Low | 19 |
The release notes list the following among the security fixes:
- Payouts: Cancelled payouts can no longer be reopened in a way that gets around pull-payment limits.
- Store isolation: Checkout forms for payment requests, Point of Sale and Crowdfund can only be chosen from the store that owns them.
- Invoices: Certain JSON reference data can no longer interrupt payment detection.
- LNURL-auth: Login and registration challenges now expire after five minutes, and are cancelled if account security details change.
- LNURL payments: Saved callbacks use the server’s configured public address instead of untrusted request headers.
- Wallet creation: The server policy that limits non-administrators to cold wallets is now enforced.
Other fixes cover two-factor login rate limiting, Lightning payment checks and protection against data exposure and resource exhaustion. See the full list in the release notes.
Check this before you update
Some changes in 2.4.7 can break existing setups. Start9’s release notes point to two:
- A route was removed. If your integration uses the old
/invoices/createroute, switch to/stores/{storeId}/invoices/create. - BitPay API reads need login. Reading a single invoice through the BitPay API now requires authentication.
The release also adds a database migration, according to Start9’s review of the update. Back up your server before you update.
How to update
- From inside the app: Go to Server Settings, then Maintenance, and click Update.
- Docker (the most common setup): SSH into the host and run the
btcpay-update.shscript from thebtcpayserver-dockerdirectory. - Umbrel, Start9 and similar platforms: Install the update once your platform offers it. StartOS has already published 2.4.7.
How the AI scan worked
Anthropic’s OSS Scanner is an opt-in service for open-source projects. Per Anthropic’s own repository, it builds a project in an isolated virtual machine with no internet access, analyses it, and emails the maintainers its findings. Each report comes with steps to reproduce the problem and, where possible, a proposed patch.
Anthropic says its models have found over 29,000 candidate vulnerabilities across open-source software in six months. Its experts could manually review only about 6,000 of them. That limit is why the service sends reports straight to maintainers who opt in. Anthropic also admits that some maintainers have told it severity ratings can be inflated, so the labels above are the scanner’s, not BTCPay’s confirmed assessment of real-world danger.
Not BTCPay’s first security release this year
Earlier in 2026, the project had to fix an actively exploited flaw involving credentials for the LND Lightning node. Versions 2.4.2, 2.4.4, 2.4.5 and 2.4.6 followed, with fixes for permissions, input handling and dependencies. Version 2.4.6 came only days before 2.4.7.
The takeaway
AI tools can now find a lot of bugs very quickly, in the hands of defenders and attackers alike. A small open-source team had to turn around 85 findings in days. The practical lesson is simple: if you run BTCPay Server, update now. Back up first, and check that your integrations still work afterwards.