60d6b616-f
BTCPay Server Rushes Out nginx Fix Covering Five Flaws
BTCPay Server patched five nginx flaws, two in HTTP/2, weeks after attackers drained hot wallets on versions 2.4.1 and earlier. The workaround covers only one CVE.

Outputs
BTCPay Server patched five nginx vulnerabilities, two affecting HTTP/2, in an emergency update.
A Linux kernel flaw could be combined with an nginx flaw for root access, researchers said.
On November 2 BTCPay urged shutdowns after hot-wallet thefts on versions 2.4.1 and earlier; the fix shipped August 7, 2026, in 2.4.2.
The @ndeet workaround disables HTTP/2 and covers only one of the five CVEs.
Umbrel and Start9 users wait on their platforms' release schedules.
BTCPay Server has shipped an emergency update patching five nginx vulnerabilities, pressing self-hosted operators to install it after a November incident in which attackers drained Bitcoin hot wallets on unpatched installations.
The project published separate installation instructions for three administrator categories. Dashboard users open Server Settings, select Maintenance and click Update, per the project's server FAQ. Operators running the standard Docker deployment sign in 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 whatever container logs it can still reach and recreates the services, keeping the five most recent successful log captures.
In the standard deployment, nginx sits in front of BTCPay Server and routes 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.
Why does HTTP/2 matter here?
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. Researchers said a separate Linux kernel vulnerability could be chained with an nginx flaw to gain root access — the highest privilege level on the host.
For operators who cannot patch immediately, BTCPay Server pointed to guidance from core contributor @ndeet. The workaround disables HTTP/2 inside the nginx container and reloads nginx after a configuration check. The contributor described the change as temporary, and the nginx release notes list fixes in other components beyond HTTP/2.
That gap matters because BTCPay Server is self-hosted payment software: every merchant, processor or node operator runs a personal instance and owns the patching burden. A flaw that needs no authentication to exploit puts every unpatched HTTP/2-enabled instance on the public internet at risk, and the workaround covers only one of the five CVEs.
What happened in November?
The timeline adds pressure. On November 2, BTCPay Server urged operators to shut down payment servers after reports of funds 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.
The first theft report arrived by email on November 1, according to the report, and the project contacted hosting providers including LunaNode to take affected instances offline as a precaution. Operators still on older builds were told to move to a fresh server with a new wallet — even without signs of theft or after updating the existing server — and to preserve logs and transaction records before replacing it.
Two security warnings in three weeks underline the operational reality of running your own payment stack: the patching burden lands on you.
What comes next?
Distribution is the checkpoint. Umbrel and Start9 users depend on those node platforms' release schedules, so their timing hinges on when each platform pushes the update. Watch whether operators who applied the HTTP/2 workaround follow through with the full nginx patch across all five CVEs — anyone relying on the workaround alone stays exposed to the resolver, HTTP/3 and mail proxy fixes.
via cryptonews.net (Source)
More from Daniel Okafor
Show full bio
Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.
1,584 articles