BTC $61,959.90 −3.24%ETH $1,754.72 −3.37%SOL $71.40 −5.09%S&P 500 7,175.83 −2.02%Nasdaq 100 26,517.00 −2.21%Gold $3,571.40 −3.73%Brent $88.97 −1.70%EUR/USD 1.0990 −0.06%DXY 103.66 −0.06%US10Y 4.98% −1.46%NVDA $145.98 −3.30%TSLA $374.41 −2.43%
FREEKONOMIST
TechLaunched

Five critical NGINX flaws found: update your servers now

Five flaws in the NGINX web server let attackers run code without logging in; fixes shipped on November 18 and BTCPay Server has pushed an emergency update.

Event: November 18, 2026
Primary source: November 18, 2026
Published here: November 19, 2026 at 08:56 AM UTC
Read: 2 min

What happened

NGINX 1.30.7 and 1.31.9 came out on November 18. They fix five flaws that let an attacker run code on a server without logging in, according to the EU's cybersecurity team, CERT-EU.

Why it matters to you

NGINX is one of the most used web servers in the world, behind many websites, exchanges and payment services. The worst bug has sat in the code since 2015 and only needs HTTP/2 turned on. Bitcoin payment software BTCPay Server has already shipped an emergency update.

What to check and watch

If you run a server, check your NGINX version and update. CERT-EU said no attacks in the wild had been reported as of November 18. If you are just a user, watch for notices from the services you use.

Where it’s happening

LIVE

Drag to spin. Green dots: the exchange is trading right now (regular hours, holidays not counted). Shadow: where it is night now. Borders: Natural Earth, quakes: USGS. Layer idea: God’s Eye View (MIT).

Flights: what adsb.lol volunteer ADS-B receivers see right now (ODbL), refreshed every minute. Few receivers over oceans and remote land; military and private jets are often hidden.

On November 18 the NGINX developers released 1.30.7 (stable) and 1.31.9 (mainline). They fix ten bugs, and CERT-EU calls five of them critical: an attacker without a login can run code with the rights of an NGINX worker process.

The bugs were found by the Xint research team. The worst one, CVE-2026-123007, is an overflow in HTTP/2 handling. An attacker only needs HTTP/2 to be enabled. Xint says it is in every official release from 1.9.5 through 1.31.8, so since 2015. The other four only work with certain settings: HTTP/3, forwarding requests to another server, or the mail proxy.

Xint showed how to chain the NGINX bug with a separate Linux kernel flaw to take full control of the machine, including breaking out of a Docker container. CERT-EU says researchers demonstrated an attack, but no exploitation in the wild had been reported as of November 18.

Who is affected. NGINX sits in front of many sites and services, including crypto payments. According to Cointelegraph, BTCPay Server, free software for accepting bitcoin on your own server, released an emergency update with NGINX 1.31.9 and asked operators to install it as soon as possible.

What to do. Update NGINX to 1.30.7 or 1.31.9. If you cannot update right away, CERT-EU suggests turning off HTTP/2 on exposed ports: that blocks two of the five bugs, not the other three. Regular website visitors do not need to do anything, this is a job for server owners.

Confirmed facts

  • NGINX 1.30.7 and 1.31.9 were released on November 18 with vulnerability fixes, including CVE-2026-123007 in HTTP/2.[1]
  • CERT-EU: five vulnerabilities let an unauthenticated attacker execute code with the privileges of the NGINX worker process.[2]
  • CVE-2026-123007 has a CVSS score of 8.1 and only requires HTTP/2 to be enabled.[2]
  • Xint says CVE-2026-123007 is in every official NGINX release from 1.9.5 through 1.31.8.[3]
  • Xint chained the NGINX bug with a Linux kernel flaw to get root on the host, including from inside a Docker container.[3]
  • No exploitation in real attacks had been reported as of November 18.[2][4]
  • Disabling HTTP/2 blocks CVE-2026-123007 and CVE-2026-123633 but not the other three bugs.[2][3]
  • BTCPay Server released an emergency update that installs NGINX 1.31.9.[4]

Implications

  • ConfirmedServer owners running NGINX need to update, and the fixes are already out.
  • Our readingThe bugs are now described in public, so the risk to unpatched servers may grow over time. This is our reading.
  • Our readingSelf-hosted crypto services like BTCPay are an obvious target because money sits there. This is our reading.

Still unknown

  • How many servers worldwide are still unpatched.
  • When every Linux distribution will ship the fixed packages.
  • Whether real attacks will follow now that details are public.

Who it affects

Global. Website and server owners, developers, crypto services and BTCPay merchants

Sources

  1. nginx.org: nginx-1.30.7 stable and nginx-1.31.9 mainline versions have been released, with vulnerability fixes November 18, 2026 · official
  2. CERT-EU: Security Advisory 2026-022: Critical vulnerabilities in Nginx November 18, 2026 · official
  3. Xint: NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching November 18, 2026 · official
  4. Cointelegraph: BTCPay Server issues emergency update for 5 security flaws November 19, 2026 · media
Cover as an image
Did this make it clearer?

Cover: Freekonomist graphic, a symbolic image, not a photo of the event. This is a news explainer, not financial advice.

More stories

Get it first on TelegramFed, jobs, inflation and big crypto moves land in the channel minutes after release. Plus a daily poll: higher or lower?Join

Morning brief by email

The night's key moves and what matters today, in 2 minutes. One-click unsubscribe.

By tapping Subscribe you agree to receive Freekonomist emails and accept the data policy.

BloFinBloFinAd · partner

Reading about markets? Try it yourself

A crypto futures exchange. Start with a small amount and low leverage: the easiest way to learn the market without extra risk.

Affiliate link: if you sign up, we may get paid. Ads never affect our exchange rating or news. Leveraged futures are high risk: you can lose everything you put in, and chasing volume for a prize adds fees and risk. 18+ only.