The Dutch National Cyber Security Centre (NCSC) has issued a warning about a series of vulnerabilities in NGINX, rating both the likelihood of abuse and the potential damage as high. It sounds like a problem for hosting companies, but NGINX turns up in more places than you might expect: behind websites and online shops, in customer portals, in hosting control panels and built into devices such as network storage. It is worth taking a moment this week to find out where it runs in your organisation.
What is going on?
NGINX is software that handles and distributes web traffic. Its developer, F5, has released updates for ten vulnerabilities. The most serious, CVE-2026-123007, lies in the way NGINX processes HTTP/2 traffic. Under certain conditions it allows an attacker to run their own code on the server without logging in. According to the NCSC, attack code is likely to appear shortly, after which widespread abuse is probable. MSP Business reports that a public proof of concept is already available.
What stands out is how long the problem has existed. Security.nl reports that the flaw has been in the software since a version released in 2015. That means many systems have been running for years without anyone looking at them again.
What does this mean for your organisation?
You do not need to have installed NGINX yourself to be affected. Consider:
- Your website or online shop, hosted by a provider or web agency.
- Customer or supplier portals and web applications that can be reached from outside.
- Devices with a web interface, such as network storage. Synology, for example, has confirmed that its NAS software contains this vulnerability.
- Servers and containers managed by your own developers or an outside party.
If an attack succeeds, someone could take over the system, read or alter data, or take the service offline. For an online shop that means lost revenue; for a portal it could mean a reportable data breach.
What can you do now?
- Make a short list of everything you have online: website, shop, portals and devices that can be reached from the internet.
- Ask your hosting provider and web agency in writing whether they use NGINX and whether the F5 update has been installed. A clear answer with a date is what you want to hear.
- Update devices as soon as the manufacturer releases a fix. Until then, follow the supplier's interim advice, such as switching off HTTP/2.
- Keep management interfaces off the internet. What cannot be reached cannot be attacked.
For more background, see Dutch IT Channel.
What Qteco does for clients
For the clients we manage, we map where NGINX is running, including inside devices and external services. We schedule updates with priority for systems that are exposed to the internet. Where a fix is not yet available, we put interim measures in place and hold the supplier to account. You receive a short overview of what has been updated and what is still outstanding.
Not sure whether your website, shop or equipment is affected? Book a conversation with one of our engineers and we will work it out together.
Sources
- Kwetsbaarheden in F5 Networks NGINX: update nu — NCSC (2026-11-18)
- NCSC houdt rekening met grootschalig misbruik van NGINX-lek — Security.nl (2026-11-19)
- NCSC waarschuwt voor misbruik van ernstig lek in NGINX Plus en NGINX Open Source — Dutch IT Channel
- Patchwork – donderdag 19 november — MSP Business (2026-11-19)
Read also
Hijacked WhatsApp accounts: how to protect your team
Ready to run worry-free?
Book a no-obligation introduction. We map your IT and security and show where the difference lies.
Book a call →
