MCAP $2.20T ▼ 3.90% Last updated 19 Nov 2026, 08:03 UTC 24H VOL $73.3B Last updated 19 Nov 2026, 08:03 UTC BTC.D 58.1% Last updated 19 Nov 2026, 08:03 UTC FEAR & GREED 10 Extreme Fear Last updated 19 Nov 2026, 00:00 UTC BTC FEE 1 sat/vB Last updated 19 Nov 2026, 08:45 UTC BTC $63,642 ▼ 1.57% Last updated 19 Nov 2026, 08:39 UTC ETH $1,803 ▼ 0.31% Last updated 19 Nov 2026, 08:39 UTC USDT $0.9993 ▲ 0.01% Last updated 19 Nov 2026, 08:39 UTC BNB $589.19 ▼ 0.47% Last updated 19 Nov 2026, 08:39 UTC USDC $0.9996 ▲ 0.01% Last updated 19 Nov 2026, 08:39 UTC XRP $0.9806 ▼ 2.00% Last updated 19 Nov 2026, 08:39 UTC SOL $74.41 ▼ 0.44% Last updated 19 Nov 2026, 08:39 UTC TRX $0.3133 ▲ 1.55% Last updated 19 Nov 2026, 08:39 UTC FIGR_HELOC $1.02 ▲ 1.59% Last updated 19 Nov 2026, 08:36 UTC HYPE $68.23 ▼ 0.31% Last updated 19 Nov 2026, 08:39 UTC

Hacks & Security · Explained

BTCPay Server pushes emergency nginx patch for five flaws

The self-hosted Bitcoin payment project told operators to install nginx 1.31.9 promptly after five flaws.

CoinDesk CC AI Desk
· 4 min read
2 sources linked
BTCPay Server pushes emergency nginx patch for five flaws

Key takeaways

  1. Emergency patch. BTCPay Server issued the update on Nov. 18 and said it installs nginx 1.31.9, while the nginx project published fixes in 1.30.7 and 1.31.9.
  2. Install routes. Operators can update from the dashboard's maintenance settings, run the Docker update script over SSH, or wait for Umbrel or Start9 to distribute it.
  3. Temporary workaround. Docker operators who cannot update immediately can disable HTTP/2 inside the nginx container and reload nginx after checking the configuration, the project said.

What happened

BTCPay Server announced an emergency update on Nov. 18 for five nginx vulnerabilities and urged operators of its self-hosted Bitcoin payment software to install it as soon as possible. The project said the update installs nginx 1.31.9. According to Crypto.news, the nginx project released fixes in 1.30.7 on its stable branch and 1.31.9 on its mainline branch. nginx is the web server bundled with BTCPay's standard Docker deployment.

Security researchers disclosed the five issues under the NGINX2Root label. Brian Pak announced the disclosure on Nov. 18. One issue, CVE-2026-123007, affects installations with HTTP/2 enabled and can let a remote attacker execute code without authenticating. The researchers said a separate Linux kernel vulnerability could be combined with an nginx flaw to gain root access, the top level of privilege on the host.

The nginx release notice lists fixes for all five issues in both open-source releases. Two of the vulnerabilities affect HTTP/2, while the other three concern HTTP/3, the resolver and the mail proxy module. Each release contains 10 security fixes in total, including the five cited by BTCPay Server. CERT-EU, the European Union's cybersecurity response team, said in a Wednesday advisory that the flaws could allow attackers to run malicious code remotely without logging in. Researchers demonstrated an exploit for one flaw, but no attacks involving the five had been reported as of Wednesday, according to Cointelegraph.

Why it matters

On the standard Docker setup, nginx receives connections on the usual web and HTTPS ports and directs traffic to BTCPay's payment application or other services configured on the same machine, according to the project's networking guide. That makes the patched software an internet-facing part of a self-hosted payment setup. The unauthenticated code-execution issue and the potential path to root access explain the project's urgency, while operators who rely on node platforms face timing set by those platforms.

What the data shows

BTCPay Server shared separate installation guidance. Administrators with dashboard access can open Server Settings, select Maintenance and click Update. Docker operators working from the command line can sign in over SSH, switch to a root shell, enter the btcpayserver-docker directory and run the project's btcpay-update.sh script. The Docker documentation says the script pulls the latest changes from the checked-out branch, saves accessible container logs and recreates services; it keeps the five most recent successful log captures. Because a saved archive reflects what was available at capture time, the guide says operators should also check the current state of services to confirm an update completed. Users on Umbrel or Start9 were told to install the update when their platform releases it. For Docker operators who cannot update immediately, core contributor @ndeet provided a temporary workaround that disables HTTP/2 inside the nginx container and reloads nginx after checking the configuration.

Background

The update follows earlier BTCPay Server security incidents involving a separate vulnerability. In August, attackers exploited a flaw to obtain credentials for Lightning Network nodes and steal funds. In November, BTCPay reported Bitcoin and Litecoin hot-wallet thefts on outdated software and said attackers had used a different method to exploit the August flaw. Crypto.news reported on Nov. 2 that the project had urged operators to shut down payment servers after theft reports; BTCPay's incident report said the first report arrived by email on Nov. 1, identified versions 2.4.1 and earlier as targeted, and dated the fix to Aug. 7, when 2.4.2 was released. The project contacted hosting providers including LunaNode and said it saw no impact on servers already running 2.4.2 or later when the warning went out.

What to watch

Operators who cannot patch immediately should treat the HTTP/2 workaround as temporary and move to the fixed nginx release as soon as their setup allows. Those relying on Umbrel or Start9 should watch for their platform's release schedule. The absence of reported attacks as of Wednesday does not remove the need to update, especially because researchers demonstrated an exploit for one of the flaws.

Questions readers ask

Which nginx flaws does the BTCPay Server update cover?

It covers five flaws disclosed under NGINX2Root, including CVE-2026-123007, an HTTP/2 issue that can allow unauthenticated remote code execution. Two affect HTTP/2; the others concern HTTP/3, the resolver and the mail proxy module.

How do I install the update?

Dashboard administrators can use Server Settings, Maintenance and Update. Docker operators can run btcpay-update.sh over SSH, and Umbrel or Start9 users should install it when their platform makes it available.

Was the vulnerability exploited?

CERT-EU said no attacks involving the five flaws had been reported as of Wednesday, though researchers demonstrated an exploit for one of them.

Sources · 2 publishers

  1. Crypto.news TIER 2 FIRST REPORT
    BTCPay Server issues emergency update for five nginx flaws
  2. Cointelegraph TIER 1
    BTCPay Server issues emergency update for 5 security flaws