BTCPay Server Plans Urgent nginx Security Update
The payment software provider will patch five nginx vulnerabilities, including an HTTP/2 flaw that can be exploited remotely without authentication.
Updated on Nov. 18, 2026 in Cybersecurity

BTCPay Server, a self-hosted payment software provider for merchants accepting Bitcoin and other cryptocurrencies, announced plans for an urgent update addressing five nginx vulnerabilities. Researchers estimate 98.9% of nginx servers with identifiable versions ran affected software.
Why it matters
The HTTP/2 flaw, dating to 2015, can be exploited remotely without authentication, and combined with a separate Linux kernel vulnerability could grant an attacker root access to the host server. Operators running nginx-dependent infrastructure face elevated risk until they apply the relevant patches.
Researchers estimate that 98.9% of nginx servers with identifiable versions ran affected software, a figure drawn only from servers whose versions could be determined. It remains unclear how many of those systems have since been updated.
The players
BTCPay Server
BTCPay Server is open-source, self-hosted payment software that lets merchants accept Bitcoin and other cryptocurrencies without relying on a third-party processor.
nginx
nginx is a widely used open-source web server and reverse proxy software that powers a large share of websites and web applications worldwide.
The details
The most serious flaw is in nginx's HTTP/2 implementation, which allows remote code execution without authentication. Chained with a separate Linux kernel vulnerability, the nginx flaw could grant root access to the host server.
Timeline
2015: The HTTP/2 vulnerability in nginx originated.
November 18, 2026: BTCPay Server announced plans for the urgent nginx patch.
The Tech Race
The disclosure of a flaw in nginx's HTTP/2 implementation shows how a protocol feature introduced in 2015 can remain a latent risk across the web server ecosystem for years. Competing server software and cloud providers face the same pressure to audit legacy protocol code.
Anyone operating a BTCPay Server or another nginx-based service should confirm their version and apply the forthcoming patches promptly. Because the flaw can be exploited without authentication, delaying the update leaves the server open to remote attack.
The takeaway
Check which nginx version your servers run and prioritize the update, since a remote, unauthenticated flaw combined with a kernel weakness can escalate to full host control. Treat legacy protocol features as ongoing risk, not settled code.
Further reading
For more on how server software flaws are tracked and disclosed, explore our Cybersecurity coverage.
Source note: This article includes information reported by TokenPost.



