Skip to content
BTCPay Server Releases Emergency Patch for Nginx Vulnerabilities

BTCPay Server Releases Emergency Patch for Nginx Vulnerabilities

First seen 19 Nov 2026, 19:50 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 19, 2026 at 19:51 UTC
  • •BTCPay Server issued an emergency patch for five critical Nginx vulnerabilities.
  • •CVE-2026-123007 allows unauthenticated remote code execution with HTTP/2 enabled.
  • •No confirmed attacks have been reported, but proof-of-concept exploits exist.

On November 18, 2026, BTCPay Server issued an emergency update to address five vulnerabilities in Nginx, including CVE-2026-123007, which allows unauthenticated remote code execution when HTTP/2 is enabled. The European Union's cybersecurity response team, CERT-EU, confirmed that while proof-of-concept exploits exist, no actual attacks exploiting these vulnerabilities have been reported. The vulnerabilities primarily affect the web server and reverse-proxy software utilized in BTCPay deployments, posing risks to payment processing and application integrity. Administrators are urged to upgrade to Nginx version 1.31.9 immediately to mitigate potential threats. Users on platforms like Umbrel or Start9 should wait for their respective updates. The advisory highlights the importance of addressing these flaws to prevent possible disruptions in payment services.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Timeline

2026-11-18
Emergency patch released
BTCPay Server released an update addressing five critical Nginx vulnerabilities, urging immediate installation.
Financefeeds
2026-11-18
CVE-2026-123007 published
The most severe vulnerability, allowing remote code execution, was disclosed with a CVSS score of 8.1.
Coinmarketcap

More articles in this cluster (2)

Following this threat?

Track BTCPay Server and CVE-2026-113425 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

What versions of Nginx are affected?
The vulnerabilities affect Nginx versions prior to 1.31.9.
How urgent is the patch?
The patch is urgent due to the potential for remote code execution without authentication.
What should I do if I can't update immediately?
As a temporary workaround, you can disable HTTP/2 in the Nginx configuration.