SECURITY ALERT
Not a bug in the wallet.
A bug in the door in front of it.
BTCPay Server, the free, self-hosted software that merchants use to take bitcoin payments, said on Wednesday that it was releasing an emergency update to fix five vulnerabilities in nginx, and told operators to update “as soon as possible”.
“We’re releasing an emergency update to address nginx CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425,” the project wrote on X at 17:29 UTC.
nginx is the web server that sits between the internet and a BTCPay instance in most setups. It is the first thing a visitor’s browser talks to.
What has been fixed
The fix arrived as a dependency change. BTCPay’s Docker deployment moved to nginx 1.31.9 in a change titled “Update Nginx to 1.31.9”, merged at 17:15 UTC, its GitHub repository shows.
nginx released 1.31.9 on 18 Nov. Its change log describes the five flaws BTCPay listed:
- CVE-2026-123007: an HTTP/2 flow-control window overflow that “might allow an attacker to cause a segmentation fault in a worker process, or might have potential other impact”. nginx’s advisory page rates it major.
- CVE-2026-123633 and CVE-2026-121810: use-after-free errors in HTTP/2 and HTTP/3 when worker connections run short.
- CVE-2026-123634: a use-after-free when the “resolver” directive is used, which could also crash a worker or have other impact.
- CVE-2026-113425: a use-after-free in nginx’s mail proxy.
A segmentation fault is a crash. “Potential other impact” is nginx’s own caution, not a claim that anyone can take over a server.
So what does this mean for a shop running BTCPay?
What nobody has said
Nobody has reported an attack on a BTCPay server through these flaws, and BTCPay has not said any funds or data are at risk.
BTCPay has not said which of its installations are exposed. nginx lists versions 1.31.9 and 1.30.7 and later as not vulnerable.
BTCPay itself has not changed version. “It was a dependency update; the next version of BTCPay is in testing,” the project said in a reply at 20:07 UTC.
The Defiant also reported the warning.
If the payment software is unchanged, how do you know you have the fix?
How to check
BTCPay gave the check in the same reply. On a Docker installation, run docker exec nginx nginx -v. The answer should be nginx version: nginx/1.31.9.
Anything older means the update has not reached that server.
The record so far
- 18 Nov. nginx publishes 1.31.9 with the security fixes.
- 18 Nov, 17:15 UTC. BTCPay’s Docker repository merges the nginx 1.31.9 update.
- 18 Nov, 17:29 UTC. BTCPay posts its emergency-update notice.
- 18 Nov, 20:07 UTC. BTCPay says the BTCPay version itself is unchanged and gives the version check.
Protect yourself
- If you run BTCPay Server yourself, update it now and confirm the nginx version is 1.31.9.
- If a hosting company runs it for you, ask them whether the nginx update has been applied.
- If you use nginx elsewhere, in front of a node, an explorer or a wallet back end, check that server too. The flaws are in nginx, not only in BTCPay’s copy.
- Take update instructions from BTCPay’s official accounts and documentation, not from a link in a message.
One web server. Five flaws. One version number to check.
When did you last look at the software standing in front of your payments?
Corrections and new evidence: [email protected]
Related: LUKSO’s key warning and Etherscan’s support-desk notice this morning · the Optimizely address-swap alert
This article is for information only and is not investment advice.
