BTCPay Server, the free, open-source payment processor that lets merchants accept Bitcoin without handing custody to a middleman, has pushed out an emergency update and is urging everyone who self-hosts it to install the fix as soon as possible.
This time the problem isn't in BTCPay's own code. The update patches five security flaws in Nginx, the widely used web server that sits in front of a typical BTCPay deployment and routes incoming web traffic to the payment application. The new release bundles Nginx version 1.31.9.
Remote Code Execution, No Login Required
The flaws were disclosed by F5, the company behind Nginx, on 18 November. In an advisory published the same week, the European Union's cybersecurity response team, CERT-EU, warned that all five could let an unauthenticated remote attacker run code on a vulnerable server with the privileges of the Nginx worker process. Each of the five carries a CVSS severity score of 8.1.
The most broadly exposed bug, CVE-2026-123007, is an integer overflow in HTTP/2 flow control that causes an out-of-bounds write on the heap. Its only precondition is that HTTP/2 is enabled on a listening port — a very common configuration for internet-facing sites. The other four are use-after-free bugs triggered under more specific setups involving HTTP/2 or HTTP/3 (QUIC) connections to upstream servers, the DNS resolver, and Nginx's mail proxy.
Security researchers have already demonstrated a working exploit for CVE-2026-123007. CERT-EU said no attacks using any of the five flaws had been reported in the wild as of its advisory — but a public proof of concept tends to shorten that window quickly.
Why It Matters for Bitcoin Merchants
A self-hosted BTCPay instance is, by design, an internet-facing server: customers' browsers have to reach it to see invoices and pay. That makes the web server in front of it the first thing an attacker touches. A remote code execution bug at that layer is exactly the kind of foothold that could be used to pivot toward the payment application and anything else on the box — including hot wallet keys, for operators who keep them on the server.
How to Apply the Fix
- Standard installs: apply the update from BTCPay's server maintenance settings, or through the Docker deployment if you manage it from the command line.
- Node-in-a-box platforms: operators running BTCPay as an app on a node platform should install the update as soon as their platform makes it available.
- Can't update yet? BTCPay has pointed operators to a temporary workaround. CERT-EU notes more generally that disabling HTTP/2 on exposed listeners mitigates two of the five flaws, including the one with a public exploit.
- Watch your logs: CERT-EU says crashing Nginx worker processes (“worker process … exited on signal”) can indicate exploitation attempts and warrant a closer look.
A Busy Few Months for BTCPay Security
The emergency release caps a rough stretch for the project. In August, attackers exploited a separate BTCPay vulnerability to obtain credentials for Lightning Network nodes and steal funds. Earlier this month, BTCPay reported hot wallet thefts from merchants still running outdated software, saying attackers had found a different way to exploit that same August flaw. The Nginx issue is unrelated to those incidents, but it lands on the same audience of merchants who have already been asked to patch several times this year.
None of this touches Bitcoin's protocol or network rules. It's a reminder that running your own payment stack is the sovereign choice, but sovereignty includes the unglamorous job of patching every layer — not just the Bitcoin software, but the web server standing in front of it.