NGINX: five critical flaws patched urgently (18/11/2026)

Published November 20, 2026 · 7 min read · CyberNovaLabs.io

Five critical flaws in NGINX, the software receiving traffic for more than 225 million websites, were fixed on 18 November 2026. Four authorities warned the same day. Your site can be exposed without having a single defect of its own.

In brief

On 18 November 2026, F5 released fixes for five critical flaws in NGINX, the software that receives traffic for more than 225 million websites. The most serious, CVE-2026-123007, lets an unauthenticated attacker run code on the server, with no password and no flaw in your own website. France's CERT-FR, CERT-EU, the Centre for Cybersecurity Belgium and the Dutch NCSC all issued warnings the same day.

What happened, in three lines

NGINX is the front door of most modern websites and APIs: it receives requests, handles HTTPS and passes traffic to the application behind it. Five memory-safety defects were found in it, disclosed together as NGINX2Root, and fixed the same day by F5 in NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline), as well as in NGINX Plus.

Two of them involve the HTTP/2 protocol. CVE-2026-123007 is a miscalculation in HTTP/2 flow control that ends in an out-of-bounds write to memory; its only precondition is that HTTP/2 is enabled on a listening port. It has been in the code since version 1.9.5, released in 2015. CVE-2026-123633 is a use-after-free flaw, reachable when NGINX proxies requests to a backend application and runs low on free connection slots.

CERT-FR states it is aware of a public proof of concept for CVE-2026-123007. CERT-EU notes that as of 18 November, no exploitation in the wild had been reported. The Dutch NCSC rated its advisory high for both likelihood and damage, writing that it expects large-scale exploitation once exploit code circulates.

Why an SME is affected even without its own server

This is the part that surprises most business owners. The flaw is not in your website: it is in the software sitting in front of it. A perfectly written brochure site, an up-to-date WordPress install, a shop with no application defect at all can still be exposed if the server delivering it runs a vulnerable NGINX version with HTTP/2 enabled.

There is a second consequence. One NGINX server usually serves several websites. On shared hosting, or on an agency's server, a single compromised machine puts every site it hosts at risk. For an SME, the risk is therefore not measured by the size of your own website, but by the size of the server it lives on.

Third point: most SMEs do not know whether they use NGINX. They very often do, because the host, the agency or the contractor installed it without it ever being a discussed decision. The question to ask is not technical, it is contractual.

What it changes, country by country

The flaw is the same everywhere, but the authority you deal with and the framework that binds you differ depending on where your business is established.

CountryAuthority and referenceWhat it says
BelgiumCentre for Cybersecurity Belgium (CCB) - advisory of 18/11/2026Titled Patch Immediately. The CCB names remote code execution as the most significant concern and points to its incident reporting form.
NetherlandsNCSC-NL - advisory NCSC-2026-0506 of 18/11/2026High likelihood, high damage. The NCSC expects large-scale exploitation as soon as exploit code circulates.
FranceCERT-FR (ANSSI) - alert CERTFR-2026-ALE-017 of 18/11/2026Recommends disabling HTTP/2 until patches are applied, and reports a public proof of concept for CVE-2026-123007.
LuxembourgLuxembourg authorities were among the national bodies relaying the alert; the reference European advisory is CERT-EU 2026-022 of 18/11/2026Update swiftly, starting with internet-facing appliances.

For a company in scope of NIS2, an event like this falls under vulnerability management and supply-chain control: you need to be able to show that you identified your exposure and acted. We offer no legal interpretation here: refer to the text applicable in your country and to your own counsel.

How to find out in ten minutes whether you are exposed

Three questions settle it, and none of them requires technical skill on your side.

  1. Does my site run behind NGINX? Your host or your agency can answer immediately.
  2. Which version, and is HTTP/2 enabled? The fixed releases are NGINX Open Source 1.30.7 and 1.31.9, and for NGINX Plus the versions listed in the F5 bulletin. If HTTP/2 is not enabled, the two HTTP/2 flaws do not concern you, but the other three may still apply depending on configuration.
  3. When was the update applied? Ask for a date, not an intention. A written answer is evidence for your file.

If the update cannot be applied straight away, CERT-FR and CERT-EU give the same interim measure: disable HTTP/2 on exposed listeners, then re-enable it once the fix is installed. That decision belongs to your provider, after compatibility testing.

To do this week

  • Monday: email your host and your web agency with a single question. Do you use NGINX, which version, and has the 18 November 2026 update been applied?
  • Tuesday: send the same request to your software providers, including anyone hosting a line-of-business tool, a client extranet or an API.
  • Wednesday: file the written answers in your security folder, with their dates. That document is what serves you in an audit or after an incident.
  • Thursday: for any server you are responsible for yourself, schedule the update with your IT contact, or the temporary disabling of HTTP/2.
  • Friday: note which providers did not reply. Silence in response to a public alert relayed by four authorities is itself information about the quality of the service.

The underlying lesson: AI is changing the tempo of vulnerabilities

The research team that reported one of the two HTTP/2 flaws states that it used AI models to find them and validate their impact, on a defect that had stayed invisible in the code for more than a decade. Several independent teams found the same flaws at the same time.

For an SME, the consequence is not theoretical: the gap between a published fix and the first exploitation attempts keeps shrinking. A patching policy that runs on a quarterly cycle is no longer enough for a component exposed on the internet. This is not a question of expensive tooling, it is a question of reflex and of contract: who watches, who applies, within what deadline, and how do they prove it to you.

We covered the same reflex in the case of the WordPress flaw exploited during the update itself, and set out what the Dutch annual report says about the widening gap between large companies and SMEs in our analysis of the CSBN 2026 report.

At CyberNovaLabs.io

We build and maintain websites and business tools for SMEs in the Netherlands, Belgium, France and Luxembourg, and security monitoring is part of the service: when an alert of this level lands, our clients get the state of their exposure without having to ask. If you do not know who among your providers owns this kind of update, that is exactly the point we clarify first. See our offer for maintained websites and business tools, or book a thirty-minute call about the real state of your estate.

Sources

  1. CERT-FR, alerte CERTFR-2026-ALE-017, Multiples vulnerabilites dans F5 NGINX (18/11/2026)
  2. CERT-FR, avis CERTFR-2026-AVI-1567, Multiples vulnerabilites dans les produits F5 (18/11/2026)
  3. CERT-EU, Security Advisory 2026-022, Critical vulnerabilities in Nginx (18/11/2026)
  4. Centre for Cybersecurity Belgium, Warning: Multiple Critical NGINX Vulnerabilities, Patch Immediately! (18/11/2026)
  5. NCSC-NL, advisory NCSC-2026-0506, Kwetsbaarheden verholpen in NGINX door F5 Networks (18/11/2026)
  6. Wiz Research, Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007 (18/11/2026)
  7. F5, Security Notification K000164058 (18/11/2026)
CyberNovaLabs.io

Qualified meetings, no lock-in.

Criteria in writing before launch, pay per meeting or monthly, stop with a simple email.

→ Get meetings booked

Read next

Newsletter · CyberNovaLabs.io

Security Briefing

One email a month: a figure from our barometer, the NIS2 and CRA dates that matter in the Netherlands, Belgium and Luxembourg, and one practical guide. In English. Unsubscribe in one click.

Talk to someone