Skip to content
Source: theregister

🚨F5 Patches 10 NGINX Bugs, Two Allow Unauthenticated Remote Code Execution

Patch your NGINX servers today, not Monday

TL;DR

F5 shipped emergency patches for 10 NGINX bugs, two allowing unauthenticated remote code execution. AI-driven researchers found them, and NGINX powers roughly a third of all websites. If you run HTTP/2, patch now.

F5 just pushed emergency fixes for 10 bugs in open source NGINX, and two of them let an attacker run code on your server with no login at all. If you're running HTTP/2 on NGINX, you're in the blast radius. Why you should care: NGINX terminates HTTPS and routes traffic for a huge slice of the internet, so a remote code execution bug there is a front-door problem. Both critical flaws, CVE-2026-123633 and CVE-2026-123007, need HTTP/2 enabled. Check that first. If you don't use HTTP/2, you have breathing room, but don't assume it's off in a config you inherited. The details: Multiple firms, including Wiz, Rapid7, Xint, Ikotas Labs, and Metnir, found these independently, and one bug has sat in the code for at least 10 years. Rapid7 published a working proof-of-concept for CVE-2026-123007, which lowers the bar for opportunistic attackers. Xint also chained a Linux kernel flaw with the NGINX bugs to reach root, which it calls nginx2root. Watch the patch backlog. AI is finding bugs faster than teams can locate vulnerable versions, test fixes, and deploy mitigations, and that gap is where breaches happen.

F5 Patches 10 NGINX Bugs, Two Allow Unauthenticated Remote Code Execution — theregister

Key Points

1

CVE-2026-123633 and CVE-2026-123007 let a remote attacker execute code on an NGINX server without authentication, provided HTTP/2 is enabled on the affected instance.

Keep reading — it's free

Enter your email to keep reading — plus the best of AI & tech, daily. Free, forever.

Also get
or

Already a member? Sign in

nginxhttp2remote-code-executioncveopen-source-security

Comments

Subscribe to join the conversation...

Be the first to comment