Cyber Incident? Get Help

5 NGINX Vulnerabilities
Let Attackers Take Control of a Server Without a Login

5 NGINX Vulnerabilities
Let Attackers Take Control of a Server Without a Login

Five vulnerabilities in NGINX, one of the world’s most widely used web servers, can let attackers take control of a server without a password or account. The most serious affects any internet-facing NGINX server with HTTP/2 turned on, a very common setup.

F5, which owns NGINX, disclosed the most serious vulnerability (CVE-2026-123007) and released fixes for all the vulnerabilities on November 18. A working attack tool was published the same day.

Coalition urges every organization that runs NGINX to patch immediately and is actively notifying policyholders whose systems are likely vulnerable.

Why this is urgent

NGINX is free, open-source software that runs a large share of the world's websites. It sits in front of websites and web applications, receiving visitor traffic and either serving pages directly or passing requests along to other systems as a reverse proxy or load balancer.

NGINX is also often built into hosting platforms, appliances, and other software, so an organization may be running it without realizing it.

This is not a theoretical risk. F5 notes that taking over a server requires getting past built-in memory protections. Coalition researchers did exactly that: Using a low-cost, publicly available AI model, we built a working exploit in under an hour and took control of a standard cloud-hosted NGINX server within 30 minutes.

Using a low-cost, publicly available AI model, Coalition researchers built a working exploit in under an hour and took control of a standard cloud-hosted NGINX server within 30 minutes.

What we know about the vulnerabilities

All five vulnerabilities are fixed in NGINX 1.30.7 and 1.31.9, according to the NGINX security advisories and F5's notification. F5 rates each vulnerability a 9.2 out of 10 (Critical). NGINX calls three of them "medium," but treats all five as critical. 

Two of the vulnerabilities (CVE-2026-123007 and CVE-2026-123633) involve HTTP/2, a newer version of the rules that web browsers and web servers use to talk to each other. Although HTTP/2 isn’t on by default in NGINX, it's almost always enabled for sites using TLS (i.e., https), which is the majority of NGINX systems on the internet. 

CVE

What it is

When it applies

Does turning off HTTP/2 help?

CVE-2026-123007

Memory error in HTTP/2 handling

HTTP/2 is on

Yes

CVE-2026-123633

Memory error in HTTP/2 handling

HTTP/2 is on and NGINX passes requests to another server

Yes

CVE-2026-123634

Memory error in DNS lookups

NGINX looks up server names from web requests while mirroring traffic

No

CVE-2026-121810

Memory error in HTTP/3 handling

HTTP/3 is on and NGINX passes requests to another server

No

CVE-2026-113425

Memory error in the mail proxy

NGINX is used as a mail proxy with login checks

No

How to determine if you’re at risk

CVE-2026-123007 is the most serious of the five. It affects every NGINX release since HTTP/2 support arrived in 2015 and needs only HTTP/2 to be turned on.

To check whether you are affected by CVE-2026-123007, look for three things:

  1. Is NGINX reachable from the internet?

  2. Is HTTP/2 turned on?

  3. Is the version older than 1.30.7 or 1.31.9?

For NGINX Plus, the fixed versions are 37.3.0.1 and 37.0.8.1. Run nginx -v to see the version and nginx -T to see the settings, then look for the word "http2." A Linux provider's version number can look old even after it has been fixed, so compare it with the provider's security notice. For the other four vulnerabilities, look in the same settings for HTTP/3, a mail proxy, or DNS lookups combined with mirroring.

Also check software that may include NGINX without saying so, such as Kubernetes ingress controllers, load balancers, vendor appliances, container images, and NGINX spin-offs like OpenResty, Tengine, Angie, and freenginx. The community "ingress-nginx" project for Kubernetes will not receive a fix, so anyone using it should turn HTTP/2 off and plan to move to a supported option.

How to resolve

  1. Forward this alert to whoever manages your systems, such as your internal IT team, managed service provider (MSP), or hosting provider, and ask them to apply the vendor's security update to every affected system.

  2. Upgrade to NGINX 1.30.7 or 1.31.9, or NGINX Plus 37.3.0.1 or 37.0.8.1. Restart NGINX after updating, because a reload keeps the old version running. The update fixes all five vulnerabilities. If NGINX is bundled inside another product or provided by a hosting platform, the update may need to come from that product's vendor or from your hosting provider.

  3. Limit exposure until the update is applied. If the affected NGINX service doesn’t need to be reachable from the internet, limit access to trusted networks or specific IP addresses. For public-facing websites this is often not practical, so applying the patch remains the priority. You can also turn off HTTP/2 by adding http2 off; to each server block (NGINX 1.25.1 or later), or by removing http2 from your listen lines, and then reloading. That blocks two of the five vulnerabilities, including the most serious, and services that need HTTP/2, such as gRPC, will stop working.

  4. Check for signs of a break-in. Warning signs include NGINX starting programs it shouldn’t, such as a command shell, repeated crashes in the error log, and a single connection that received tens of gigabytes of data. Coalition policyholders who find signs of compromise should contact the Coalition claims team right away.

Next steps

Coalition will continue monitoring and doing proactive outreach to policyholders that are running NGINX and appear to be exposed. We will update this guidance as new information emerges.


EASILY SPOT & STOP CYBER THREATS IN ONE PLACE

Coalition Control

Take control of your cyber risk >


This blog post is designed to provide general information on the topic presented and is not intended to construe or render legal or other professional services of any kind. If legal or other professional services are required, the services of a professional should be sought. Descriptions of coverage are for general informational purposes only and are subject to the terms and conditions, including the limitations and exclusions, of the applicable policy. The reader is cautioned to consult independent professional advisors and formulate independent conclusions and opinions regarding the subject matter discussed herein. Coalition makes no representations as to the accuracy or completeness of this content. Any action taken based on this information is at the sole discretion and risk of the reader. Coalition and its affiliates expressly disclaim any liability for losses or damages resulting from the use of or reliance on this information, which is used strictly at the reader’s own risk. The blog post may include links to other third-party websites. These links are provided as a convenience only. Coalition does not endorse, have control over nor assume responsibility or liability for the content, privacy policy or practices of any such third-party websites.
Copyright © 2026. All rights reserved. Coalition and the Coalition logo are trademarks of Coalition, Inc.

Related blog posts

See all articles
Security

Blog

Cyber Criminals Left Their AI Hacking Tools Open to the Internet

Coalition security researchers found thousands of AI hacking harnesses on the open internet. The discovery carries implications for the future of cyber risk.
Tiago HenriquesNovember 06, 2026
Security

Blog

What You Need to Know About the European Fridge Hacks

Europe is experiencing another round of cyber attacks on fridges. How far does the threat travel, who is at risk, and how does insurance respond?
Nepomuk LoestiNovember 06, 2026
Security

Blog

Why PHP2Shell Claims Will Lag Exploits by Weeks

Cyber insurance claims from PHP2Shell haven’t arrived en masse yet. Did we overhype the PHP vulnerabilities or is this the calm before the storm?
Tiago HenriquesNovember 02, 2026