How operators can install the fix
BTCPay Server issued separate instructions for three kinds of administrator. Those with dashboard access open Server Settings, select Maintenance and click Update, per the project’s server FAQ.
Operators running the standard Docker deployment sign in to the host over SSH, switch to a root shell, change into the btcpayserver-docker directory and run btcpay-update.sh. The project’s Docker documentation says the script pulls the latest changes from the checked-out branch, saves the container logs it can still reach and recreates the services. It keeps the five most recent successful log captures.
In the standard deployment, nginx sits in front of BTCPay Server and directs incoming web requests to the payment application or to other services on the same installation. The project’s networking guide identifies nginx as the component handling incoming connections on the standard web and HTTPS ports.
Users who depend on a node platform for updates were told to follow that platform’s release schedule. BTCPay Server recommended urgency, but for Umbrel and Start9 users the timing depends on when the platform distributes the update.
HTTP/2 is the centre of the problem
Two of the five nginx vulnerabilities affect HTTP/2, according to the nginx release notice. The remaining three concern HTTP/3, the resolver and the mail proxy module. The researchers said a separate Linux kernel vulnerability could be combined with an nginx flaw to gain root access, the highest privilege level on the host.
For operators who cannot install the update immediately, BTCPay Server pointed to guidance from core contributor @ndeet. That workaround disables HTTP/2 inside the nginx container and reloads nginx after checking the configuration. The contributor described the change as temporary, and the nginx release notes list fixes in other components beyond HTTP/2.
Why it matters
BTCPay Server is self-hosted payment software: each merchant, processor or node operator runs their own instance and bears the responsibility for patching it. A flaw that requires no authentication to exploit puts every unpatched HTTP/2-enabled instance at risk on the public internet, and the temporary workaround covers only one of the five CVEs.
The timing adds pressure. On November 2, BTCPay Server urged operators to shut down payment servers after reports of funds being taken from Bitcoin hot wallets on older installations. The project’s incident report identified BTCPay Server 2.4.1 and earlier as the targeted versions and dated the fix to August 7, 2026, in version 2.4.2. It said the first theft report arrived by email on November 1 and that it had contacted hosting providers, including LunaNode, to take affected instances offline as a precaution.
Operators still on those older builds when that warning went out were told to move to a fresh server with a new wallet, even if they saw no theft or updated the existing server afterward. The incident report also asked affected operators to preserve logs and transaction records before replacing the old server. Two security warnings in three weeks is a useful reminder that running your own payment stack shifts the patching burden onto you.
What to watch
The next checkpoint is distribution: when Umbrel and Start9 push the update to their users, and whether operators who applied the HTTP/2 workaround follow up with the full nginx patch across all five CVEs. Anyone relying on the workaround alone remains exposed to the resolver, HTTP/3 and mail proxy fixes.