Market cap $2.20 T −3.48 % over 24 hours24h volume $73.58 BBTC dominance 58.1 %ETH 10.0 %Fear & Greed 10 Extreme fearCoins 21,490

BTCPay Server ships an emergency nginx update: its version number stays at 2.4.7, so check the container

BTCPay Server moved its Docker nginx to 1.31.9 on 18 November to fix five CVEs. Its own version stays 2.4.7, so operators must check the container.

8 min read

Abstract broken chain beside a wallet, connected network nodes and a turning gear
Table of contents
  1. What BTCPay changed on 18 November
  2. The five nginx flaws, in nginx’s own words
  3. How to update BTCPay Server and check the nginx version
  4. The HTTP/2 workaround covers two flaws out of five
  5. A different problem from the November hot-wallet thefts
  6. What is still unknown

BTCPay Server, the open-source payment processor that merchants host themselves, told its operators on Wednesday 18 November 2026 to update “as soon as possible”. The BTCPay Server nginx update replaces the web server shipped with the project’s Docker deployment, moving it from nginx 1.31.8 to 1.31.9, which nginx released the same day to fix ten security flaws. BTCPay names five of them in its notice. No attack using them has been publicly confirmed, the project says.

The fix does not touch BTCPay Server itself. The latest release on GitHub is still 2.4.7, published on 29 October, and the number shown in the dashboard footer will not move. An operator who reads “2.4.7” and concludes that the server is up to date may still be running the old web server underneath.

What BTCPay changed on 18 November

The change is a single pull request in the btcpayserver-docker repository, titled “Update Nginx to 1.31.9”. GitHub shows it opened at 17:01 UTC and merged at 17:15 UTC on 18 November, fourteen minutes later. Core contributor ndeet approved it with the note that he had edited the nginx file, run the setup script “and it worked”. The request, filed by the account r1ckstardev, switches the official image to nginx:1.31.9-trixie. Its description gives the reason in one line: the new version fixes two HTTP/2 vulnerabilities, CVE-2026-123007 and CVE-2026-123633.

The public notice followed on X at 17:29 UTC, a quarter of an hour after the merge. “We’re releasing an emergency update to address nginx” flaws, the BTCPay Server account wrote, listing five identifiers: CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425. The project’s blog carries no post on the subject; the thread and the pull request are the notice.

Later in the same thread, BTCPay credited the accounts @Rob1Ham and @danielabrozzoni and the rest of the Bitcoin Red Team for watching open-source software and alerting projects to the nginx flaws. It also thanked its funders, saying their support lets it keep up with security updates.

The five nginx flaws, in nginx’s own words

nginx sits in front of BTCPay Server in the Docker setup: it receives the connections from customers’ browsers and passes them on. The nginx security advisories page rates two of the five flaws “major” and three “medium”. All five are fixed in 1.31.9 on the mainline branch and in 1.30.7 on the stable branch.

CVEWhat nginx calls itnginx severityVulnerable versions
CVE-2026-123007Memory corruption in HTTP/2 flow controlMajor1.9.5 to 1.31.8
CVE-2026-113425Use-after-free in mail proxy moduleMajor0.5.33 to 1.31.8
CVE-2026-123633Use-after-free in HTTP/2Medium1.19.7 to 1.31.8
CVE-2026-121810Use-after-free in HTTP/3Medium1.25.0 to 1.31.8
CVE-2026-123634Use-after-free during response processing in resolverMedium0.6.18 to 1.31.8

The one that drew attention is the first. The nginx changelog says a flow control window overflow in HTTP/2 “might allow an attacker to cause a segmentation fault in a worker process, or might have potential other impact”. It credits Xint.io for the report, and names the firm again for the HTTP/3, resolver and mail proxy flaws. The version range starts at 1.9.5, the release that brought HTTP/2 to nginx in 2015, according to BigGo Finance.

Abstract server rack with a bug under a magnifying glass and a warning sign
nginx rates the HTTP/2 flow control flaw major and credits Xint.io for reporting it.

The changelog attaches conditions to the others. The HTTP/2 and HTTP/3 use-after-free flaws can occur, it says, when the server runs short of worker connections. The resolver flaw needs the resolver directive and an attacker able to trigger name lookups. The fourth sits in the mail proxy server, a part of nginx separate from the web server role. BTCPay does not say which of the five its default configuration exposes.

BTCPay’s list stops at five, but the image fixes ten. Among the five it does not name, nginx rates one major: CVE-2026-118899, which can leave worker processes stuck in an endless loop while they read a request body over TLS 1.3. The other four are two flaws in the stream module, one in PROXY protocol handling and one in the pairing of the alias and try_files directives; nginx rates one of them medium and three minor.

nginx does not use the words “remote code execution”. The researchers do. crypto.news and BigGo Finance both report that the findings were disclosed under the name NGINX2Root and announced by researcher Brian Pak on 18 November; BigGo names the security firm Xint as their author. According to crypto.news, CVE-2026-123007 can let a remote attacker execute code without authenticating on a server where HTTP/2 is enabled. BigGo adds that the code would run with the privileges of the nginx worker process. Both say a separate Linux kernel bug could be chained to an nginx flaw to reach root. That is the finders’ description as two outlets relay it. The nginx advisory gives a severity word and a version range, with no numeric score.

BTCPay’s own reading is more measured. “We understand that the referenced Nginx exploits are fragile and that, so far, no attacks have been publicly confirmed,” the project wrote in its thread, adding that it would always act as soon as it could to give users a remedy.

How to update BTCPay Server and check the nginx version

BTCPay gives two routes in its thread, and they match the update procedure in its documentation. The third step below is not BTCPay’s: it is the ordinary way to ask a container which nginx it runs.

  1. From the dashboard, a server admin opens Server Settings, then Maintenance, and clicks Update.
  2. On a Docker server, which BTCPay describes as “most servers”, log in over SSH and run sudo su -, then cd btcpayserver-docker, then btcpay-update.sh.
  3. Then read the version on the container, since the BTCPay version will look the same as before. The thread gives no command for this; the standard Docker one is docker exec nginx nginx -v, which should print nginx version: nginx/1.31.9.

Two details support that check. The merged pull request sets the image to 1.31.9, so that is the number a patched container reports, and nginx is the container name ndeet’s own workaround commands use. nginx -v is the web server’s version flag.

People who run BTCPay Server as an app on a node platform are in a different position. BTCPay names Umbrel and Start9 and tells their users to install the update as soon as their platform makes it available. The thread says nothing more about either platform.

One snag is documented for the script route. If a file in the btcpayserver-docker folder was edited by hand, the update can stop with the error “Your local changes to the following files would be overwritten by merge”. BTCPay’s documentation gives the way out: run git reset --hard origin/master in that folder, which discards the local edits, then update again.

Abstract laptop beside a shield, an hourglass and a cloud shape
Admins of Docker servers can update now; BTCPay tells Umbrel and Start9 users to install the fix when their platform offers it.

The HTTP/2 workaround covers two flaws out of five

For operators who cannot update at once, BTCPay relays a stopgap published by ndeet, who labels it “TEMPORARY” and “non persistent” and wrote that it was for use “until nginx release available”. It is two commands. The first uses sed to rewrite /etc/nginx/conf.d/default.conf inside the container, changing “http2 on” to “http2 off”; the second tests the configuration with nginx -t and, if the test passes, reloads nginx.

Its limits are plain from the table above. Only CVE-2026-123007 and CVE-2026-123633 are HTTP/2 flaws. BigGo Finance, citing Xint, reports that the workaround covers those two and leaves CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425 open, and that the change does not survive the replacement of the container.

A different problem from the November hot-wallet thefts

This is the second urgent notice to the same audience in November. On the 2nd, BTCPay told operators of version 2.4.1 and earlier to shut their servers down after hot wallets were emptied. BTCPay’s thread draws no link between the two, and BigGo Finance reports that the project describes the thefts as unrelated to the nginx flaws. That episode came from BTCPay’s own code and was fixed in a BTCPay release; this one sits in a third-party web server and is fixed by a new container image. A server still on 2.4.1 or earlier has the older, more serious problem to solve first.

Both land on the same people: merchants who chose self-custody and run the payment server themselves, often with a hot wallet on the same internet-facing machine. No processor patches it for them, down to the web server. Ethereum node operators got a similar order on 11 November, when Lighthouse asked every beacon node to upgrade without saying why.

What is still unknown

nginx has not published a numeric severity score for the five flaws, only its own major and medium labels. No public attack has been confirmed, by BTCPay’s account, and neither crypto.news nor BigGo Finance reports one. BTCPay has not said how many servers run the affected image or which of the five flaws its default configuration exposes, and its thread gives no date for the Umbrel and Start9 packages. The pull request cites two CVEs, the notice five.

Sources

  1. X post by @BtcpayServer, 18 November 2026 x.com
  2. btcpayserver-docker pull request #1255, "Update Nginx to 1.31.9" (GitHub, merged 18 November 2026) github.com
  3. nginx security advisories (nginx.org) nginx.org
  4. nginx CHANGES, version 1.31.9 of 18 November 2026 (nginx.org) nginx.org
  5. crypto.news, BTCPay Server nginx emergency update, 18 November 2026 crypto.news
  6. BigGo Finance, BTCPay Server emergency update for five nginx flaws, 18 November 2026 finance.biggo.com

Leave a Reply

Your email address will not be published. Required fields are marked *