Xint, the research team that disclosed the flaws, said CVE-2026-123007 allows an unauthenticated attacker to execute commands with the nginx worker process's permissions when HTTP/2 is enabled on an affected server. The other findings involve a second HTTP/2 flaw, HTTP/3, the DNS resolver and the mail proxy; they affect different configurations.
In a follow-up post, BTCPay said it understood that no attacks using the referenced nginx exploits had been publicly confirmed so far.
Loading post from X…
View post on X
How to Apply and Check the Update
BTCPay published instructions for three update routes:
-
Web dashboard: Server administrators should open Server Settings → Maintenance → Update.
-
Docker over SSH: Log in to the host, switch to a root shell with
sudo su -, enter the btcpayserver-docker directory and run btcpay-update.sh.
-
Node platforms: Users of Umbrel, Start9 and similar platforms should install the update as soon as their platform makes it available.
The Docker updater pulls the latest changes from the checked-out branch and recreates the services. To check the nginx version afterward, BTCPay said to run docker exec nginx nginx -v. The expected output is nginx version: nginx/1.31.9.
For separately managed nginx installations, the upstream release notice lists fixes in stable version 1.30.7 and mainline version 1.31.9. Distribution packages may instead backport the fixes; Xint advises checking the full package version against the distribution's advisory and restarting nginx after installation, rather than only reloading its configuration.
BTCPay also endorsed a temporary workaround from core contributor @ndeet for Docker operators unable to patch immediately. The nonpersistent workaround changes http2 on to http2 off in the default nginx configuration file, tests the configuration and reloads it if the test passes. Operators with custom configurations should follow Xint's guidance to disable HTTP/2 on every affected listener, including legacy listen settings. Xint cautions that disabling HTTP/2 blocks only two of the five flaws, not the other three.
Earlier Wallet Drains Require More Than a Patch
The alert follows this month's shutdown warning after reports of Bitcoin and Litecoin thefts from hot wallets, which hold spending keys on the server. BTCPay's Nov. 2 incident report said those attacks targeted BTCPay 2.4.1 and earlier, exploiting a vulnerability fixed in version 2.4.2 on Aug. 7.
The Nov. 2 report advised operators still running 2.4.1 or earlier, or who updated from those versions after the Nov. 1 warning, to move to a fresh server with a new wallet, even if no theft was noticed. Its recovery steps include sweeping remaining hot-wallet funds, taking the old server offline and replacing potentially exposed credentials.
BTCPay gave the same advice to anyone with stolen funds or signs of unauthorized access, even after updating. Updating alone cannot remove access an attacker may already have gained, the project said.