NGINX’s Critical HTTP/2 Flaws Let Attackers Run Code Without Logging In — Patch Now

Two critical flaws in NGINX — the web server that powers a huge share of the internet — let an unauthenticated attacker run code on any affected server with HTTP/2 enabled. Fixes were released on Wednesday, November 18, and a proof of concept for one of the flaws is already public. If you run anything internet-facing on NGINX, this is the patch to do first today.

Two Flaws, One Protocol

The two critical-rated flaws are CVE-2026-123007 and CVE-2026-123633, according to the research teams at Wiz and Xint. Both require HTTP/2 to be switched on, and both allow remote code execution without any login. One of the flaws has been sitting in the code since 2015 — more than a decade of exposure in one of the most widely deployed pieces of software on the internet.

F5, which maintains NGINX, released fixes on November 18 covering ten vulnerabilities in total, in releases 1.31.9 (mainline) and 1.30.7 (stable). F5 told The Register it has seen no exploitation so far. That is reassuring, but it is not a reason to wait: with a proof of concept now public, the window between disclosure and real-world attacks is usually measured in days, not weeks.

Why This One Is Different

Patching NGINX has two traps that catch even experienced teams. First, a reload does not replace the running binary — a patched package that was only reloaded is still vulnerable in memory. The fix only takes effect after a full restart. Second, distribution packages often carry the fix under an old version number, so checking nginx -v can mislead you into thinking you are patched when you are not.

Turning HTTP/2 off is a stopgap for the two critical flaws, but not for all five that Xint rates critical. The safe course is to patch and restart, then verify the running process is actually the new build. Treat this as an urgent patch on anything internet-facing, even with no reported exploitation yet.

A Proof of Concept Is Already Public

Rapid7 has published a proof of concept for one of the flaws, according to The Register’s reporting. That changes the calculus. Once exploit code circulates, automated scanning follows quickly, and every unpatched NGINX server with HTTP/2 exposed becomes a target — including copies bundled inside appliances and container images that teams forget to inventory.

Start with an inventory: find every NGINX instance you run, including the ones hidden inside appliances and container images. Then schedule restarts, not reloads, after patching, and confirm the new binary is actually running.

The Rest of This Morning’s Security News

NGINX is the headline, but it is far from the only item on today’s list.

CISA added two more flaws to its Known Exploited Vulnerabilities catalogue on Wednesday, both with a federal due date of Saturday, November 21. The first is CVE-2026-90436, an unsafe-reflection flaw in Apache Axis 1.x. Rapid7 says its managed detection team saw it used against a customer’s Atlassian Confluence Data Center on November 13, and N-able reported exploitation against N-central the same day. Atlassian’s advisory says Confluence is exposed only if the Remote API setting is enabled — off by default for new installs since Confluence 3.0 — and lists 9.2.28 as the fixed Data Center version. The second is CVE-2024-10441, a critical code-execution flaw in Synology DiskStation Manager, rated CVSS 9.8, with no mitigation — only a firmware update, with fixed releases including 7.2.2-72806-1.

PHP is preparing critical security updates for all supported versions, scheduled for today, November 19, between 14:00 and 14:30 UTC, for a flaw affecting session upload progress. Google released Chrome 158 to the stable channel, patching 204 vulnerabilities, including six critical-severity bugs.

On the incident side, Infoblox told The Register it is investigating unauthorised access to company information through a compromised third-party data migration vendor. The vendor reportedly had trusted access to Infoblox’s SharePoint, and the intruders used its accounts to take data directly, including saved NIOS snapshots — backups of DNS, DHCP and grid configuration — for some customers, plus employee data. Infoblox says it has found no sign that its products, cloud services, software updates or build process were involved.

And Microsoft has put Windows Server 2028 into public preview, with Server Core installs hardened from first boot, aligned with CIS and DISA STIG benchmarks. Microsoft’s own warning is plain: because the defaults are locked down, some things that worked on Windows Server 2025 may not work on Windows Server 2028 without changes, including older protocols, legacy authentication and some management tools and scripts.

What to Do Before Lunch

First, inventory NGINX everywhere — servers, appliances, container images — and patch to 1.31.9 or 1.30.7, then restart the service and verify the new binary is running. Second, check Confluence for the Remote API setting and Synology NAS units for firmware before Saturday’s CISA deadline; if a NAS faces the internet, take it offline until it is current. Third, prepare for the PHP updates landing this afternoon and update Chrome to version 158. Finally, if you are an Infoblox customer, ask the company directly whether your NIOS snapshots were among those taken — and treat any configuration backup as a credential store, rotating shared secrets and API credentials if the answer is yes or unclear.

The Bottom Line

Two unauthenticated remote code execution flaws in NGINX — one of them hiding in the code since 2015 — now have fixes and a public proof of concept. Patching is not optional, and a reload is not enough: restart the service and verify the new build is running. With CISA deadlines landing Saturday, PHP updates due today and Chrome patching 204 flaws, this is a morning for patching first and asking questions later.

Sources: KBY Technologies IT Morning Briefing, November 19, 2026 (reporting on Wiz and Xint research, F5/NGINX advisories, The Register, Rapid7, CISA, Atlassian and Synology advisories); Security Daily (SecHOT), November 19, 2026; Cyber Security News / SecOraLens advisories, November 19, 2026.

Edited by Muse @QUE.COM
Website: https://QUE.COM Intelligence
Sponsored by: https://MAJ.COM AI Autonomous
Never miss a customer call again — MAJ.COM’s AI receptionist answers every call, texts customers back instantly, and books the appointment for you. See how it works at https://MAJ.COM


Discover more from QUE.com

Subscribe to get the latest posts sent to your email.

Leave a Reply

Connect with

Discover more from QUE.com

Subscribe now to keep reading and get access to the full archive.

Continue reading