BTCPay has upgraded Nginx to 1.31.9 in its Docker deployment. CERT-EU’s November 18 advisory said no exploitation in the wild had been reported.
BTCPay Server, software for accepting Bitcoin payments, has updated its Docker deployment to address security flaws in Nginx. A change merged on November 18 upgrades the component that handles incoming web traffic to version 1.31.9. The update concerns payment-server software, not the Bitcoin network.
BTCPay is an open-source payment processor that merchants can run on their own servers. In the standard deployment, Nginx receives incoming web requests and directs them to the appropriate service. Checking the BTCPay application version alone does not establish whether the web-server component has been patched.
Which servers are exposed depends on their settings
In its November 18 advisory, CERT-EU said an unauthenticated attacker could execute code with the permissions of the Nginx worker process on vulnerable systems with the required features enabled. Researchers had demonstrated exploitation of one flaw, but the agency said no exploitation in the wild had been reported at publication. The researchers’ demonstration does not establish that a particular merchant’s server was compromised.
Exploiting CVE-2026-123007 requires a vulnerable Nginx server that accepts HTTP/2 connections. A flaw in flow control can make the program write outside its allocated memory and disrupt its operation. The other vulnerabilities require different features, and do not affect every BTCPay installation equally.
| Vulnerability | Relevant server function |
|---|---|
| CVE-2026-123007 | Managing data flow in HTTP/2 connections |
| CVE-2026-123633 | Proxying HTTP/2 requests to an upstream server |
| CVE-2026-121810 | HTTP/3 and QUIC connections |
| CVE-2026-123634 | Dynamic DNS resolution combined with SSI or mirror subrequests |
| CVE-2026-113425 | Using Nginx as a mail proxy |
Red Hat’s technical bulletin asks operators to assess HTTP/2, HTTP/3, mail proxying and dynamic name resolution separately. Nginx instances serving only static files without those features are not affected by these five vulnerabilities. The announcements did not give an affected-server count or report a new loss for BTCPay users.
The BTCPay update installs Nginx 1.31.9
The code change replaces the Docker image nginx:1.31.8-trixie with nginx:1.31.9-trixie. That version identifies Nginx, rather than the BTCPay application number displayed in the dashboard. Nginx’s official security list identifies 1.31.9 and 1.30.7 as patched releases for the five flaws.
Server administrators can follow BTCPay’s update instructions: open Server Settings, select Maintenance and click Update. Operators managing a Docker installation over SSH can run btcpay-update.sh from the btcpayserver-docker directory on their server. Those who installed through a platform such as Umbrel or Start9 should install the update when their platform makes it available.
If patching is not immediately possible, CERT-EU says disabling HTTP/2 on exposed listeners temporarily mitigates CVE-2026-123007 and CVE-2026-123633. It does not fix the HTTP/3, DNS resolver or mail proxy flaws. Changing settings and reloading the service is also different from installing the patched software.
Earlier wallet thefts involved a different vulnerability
BTCPay’s November 2 incident report described Bitcoin and Litecoin thefts from hot wallets on version 2.4.1 and earlier. Attackers had exploited a different flaw fixed in 2.4.2 on August 7. A hot wallet keeps the private keys needed to spend funds on the server. The Nginx update does not establish that the earlier thefts have happened again.
The team had advised affected operators to use a fresh server and wallet and replace potentially exposed credentials. It said wallets with spending keys kept off the server, including hardware wallets, were unaffected by those thefts. Patching an already compromised server, however, does not by itself remove access an attacker previously gained.



















