BTCPay Ships an Emergency Update for Five Nginx Flaws at CVSS 8.1

The flaw that matters most needs nothing from an attacker but an open port. BTCPay Server pushed an emergency update on 18 November for five vulnerabilities in nginx, the software that routes inbound web traffic to its payment application, and told operators of its self-hosted Bitcoin payment stack to install it at once. Each of the five carries a CVSS severity score of 8.1, and all five can end in unauthenticated code execution with the privileges of an nginx worker process. The update installs nginx 1.31.9. Nothing in Bitcoin itself is involved, nor in BTCPay's wallet code.
Five flaws, one score
The identifiers are CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425. CERT-EU, the European Union's cybersecurity response team, published its advisory on the set the same day and describes the first as an integer overflow in HTTP/2 flow control that causes an out-of-bounds write on the heap. Its only precondition is HTTP/2 enabled on a listening port, which gives it the widest reach of the five. CVE-2026-123633 is a use-after-free that fires when connection draining closes an active HTTP/2 connection while nginx is talking to a server behind it. The other three are narrower, each needing a particular configuration: QUIC handling for HTTP/3 backends, the DNS resolver's waiting list, the authentication lookup a mail proxy performs. Some of the secondary coverage calls the first flaw memory corruption; the advisory is specific that it is an integer overflow.
The affected range is long. CERT-EU lists nginx mainline from 1.9.5 through 1.31.8, the whole 1.30.x stable series and several NGINX Plus releases. Cryptopolitan alone dates the worst flaw to 2015, when HTTP/2 arrived in 1.9.5.
Turning off HTTP/2 closes two doors of five
BTCPay pointed operators who cannot patch at once to a temporary workaround, and the workaround is partial. CERT-EU is explicit that disabling HTTP/2 on exposed listeners mitigates CVE-2026-123007 and CVE-2026-123633, leaving the DNS, HTTP/3 and mail-proxy flaws untouched. Cryptopolitan adds that it stops applying once the container is replaced. The real fix goes in through server settings and maintenance, or a Docker update script. Operators on node platforms such as Umbrel or Start9 must wait for those to ship it.
"It is recommended to swiftly update NGINX as soon as possible, prioritising internet facing appliances," the CERT-EU advisory said.
Ten or five, depending on who counted
The number of holes nginx itself plugged does not agree across the reporting. FinanceFeeds writes that nginx released stable 1.30.7 and mainline 1.31.9 on 18 November, addressing ten security vulnerabilities across its software. Cryptopolitan writes that both versions fixed all five. The advisory covers five and refers readers to the vendor's own for fixed versions without giving a count, so it settles neither reading. The totals do not reconcile, and we could not establish which belongs to that release. On exploitation the accounts agree: researchers demonstrated an attack against CVE-2026-123007 in work published the same day, and CERT-EU said none had been seen in the wild. That was the position as of 18 November.
What a patch cannot undo
This is the third BTCPay security event of the autumn, and the earlier two were not nginx. In August attackers exploited a BTCPay flaw to lift the credentials that Lightning Network Daemon nodes use, known as macaroons, and funds were stolen; the project then restricted certain remote Lightning connections, a pattern other implementations followed in blocking browser requests to a Lightning node API. On 1 November came reports of Bitcoin and Litecoin taken from hot wallets on servers running version 2.4.1 or older, with $1.63 million traced by one analytics firm and no loss total confirmed by the project itself.
Nobody has said how many installations still run the vulnerable nginx, and no loss has been attributed to any of the five flaws. What a compromised worker process would reach is unsettled too: FinanceFeeds notes that code execution inside nginx does not by itself hand over private keys or control of the host. For a merchant running a checkout, the nearer cost is a payment page that stops answering.
Read also: Bitcoin Core Discloses Three Patched Flaws, Including a Mining Bug