Unauthenticated Remote Code Execution In Nginx
AIThis post was created with the assistance of artificial intelligence (AI).

TL;DR

Researchers disclosed two critical NGINX vulnerabilities, CVE-2026-123633 and CVE-2026-123007, that can allow unauthenticated remote code execution when HTTP/2 is enabled. F5 published security updates on November 18, 2026; organizations are advised to identify affected deployments, patch them, or temporarily disable HTTP/2 if they cannot upgrade promptly.

F5 and security researchers disclosed two critical NGINX vulnerabilities on November 18 that can let an unauthenticated remote attacker execute code on affected servers when HTTP/2 is enabled. The flaws, tracked as CVE-2026-123633 and CVE-2026-123007, put web and API services behind vulnerable NGINX deployments at risk; F5 released security fixes and researchers advised organizations to patch promptly.

Before you orderOffer from Amazon

Get privacy and security gear delivered free with Prime

  • Fast, free delivery on millions of items
  • Prime Video, Amazon Music and more included
  • Member-only deals all year
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

The two flaws are rated Critical and each has a CVSS 4.0 score of 9.2, according to the Wiz report. Both affect NGINX itself rather than application code, so a website can be exposed even if its own software is secure. The reported attack prerequisite is that HTTP/2 is enabled on the affected NGINX server. Wiz said successful exploitation could give an attacker control of the server, with possible consequences including data theft, website tampering, and service disruption.

Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered the vulnerabilities and reported them to F5, the company behind NGINX. Wiz said it demonstrated code execution for CVE-2026-123007 on a server serving ordinary static files, without a backend application or third-party modules. That test indicates the risk is not limited to deployments that use a particular application framework, though exposure still depends on the affected server and configuration.

The reported flaws have different histories. CVE-2026-123007 affects versions dating back to NGINX 1.9.5, released in 2015, according to Wiz. The other issue, CVE-2026-123633, is described by the researchers as an HTTP/2 use-after-free vulnerability that had been present for nearly six years. Wiz’s disclosure timeline says it first reported the use-after-free issue to F5 on October 21, 2026, and submitted the second finding on November 16. F5’s security release and the coordinated public disclosure followed on November 18.

At a glance
updateWhen: Security release and coordinated disclo…
The developmentF5 and security researchers publicly disclosed two critical NGINX HTTP/2 vulnerabilities on November 18, 2026, after coordinated reporting and remediation.

Why NGINX Exposure Can Spread

NGINX commonly sits at the front of web and API infrastructure, receiving HTTPS traffic and routing requests to services behind it. A successful compromise of that layer could affect more than one application hosted through the same deployment. The potential reach depends on how each organization has built and isolated its systems; the available report does not establish that every deployment has the same level of exposure.

The vulnerabilities also matter because they are in a widely used server component, not necessarily in the code written for a specific website. Wiz says NGINX powers more than 225 million websites. That figure describes the software’s reported reach, not the number of systems confirmed vulnerable. Still, organizations should check their NGINX versions and HTTP/2 settings rather than assume secure application code protects the traffic-handling layer.

For defenders, the immediate issue is reducing exposure and applying the supplied fixes. Wiz recommends identifying affected deployments, prioritizing systems reachable by attackers, and moving updates through production. If a patch cannot be installed immediately, the report recommends temporarily disabling HTTP/2. Such a change may affect traffic handling or compatibility, so organizations need to assess it against their own services.

Products Worth Considering

Kindle Paperwhite Signature Edition 32GB (2024 Model) - Metallic Black

Kindle Paperwhite Signature Edition 32GB (2024 Model) – Metallic Black

As an affiliate, we earn on qualifying purchases.

How Disclosure Reached November 18

Wiz reports that it disclosed CVE-2026-123633 to F5 on October 21, 2026, including what it described as confirmed remote code execution, an ASLR bypass, and a proposed fix. F5 told Wiz another research team had previously reported the same issue. F5 supplied a patch for review on November 10, according to the timeline.

Wiz reported the second vulnerability on November 16. On November 17, F5 confirmed that it matched CVE-2026-123007 and was included in the planned security release. F5 published the release alongside coordinated disclosure on November 18. The source says the researchers used Wiz Atlas to find the flaws and used Gemini 4 Carbon and ChatGPT 5.6 Sol to validate impact. These details are the report’s account of the research process, not independent evidence that AI tools alone discovered or verified the flaws.

Wiz frames the findings as examples of memory-safety issues that can be difficult to trace through complex code paths. That broader interpretation comes from the researchers. The confirmed development covered here is the disclosure of two vulnerabilities, their reported impact and prerequisites, and the availability of F5’s security release.

“Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server.”

— Wiz Research

Exposure Depends on Deployment

The disclosure does not state how many NGINX servers are vulnerable, how many have been patched, or whether attackers have exploited either flaw in the wild. It also does not establish that every installation with HTTP/2 enabled is exploitable: affected version, configuration, and the precise conditions for successful exploitation need to be checked against F5’s security advisory and the relevant release notes.

The source material summarizes the vulnerabilities and patch timeline but does not list the full affected-version ranges or identify specific fixed version numbers. It also does not provide independent confirmation of the research claims about code execution or observed attacks. Organizations should use F5’s advisory for version-level guidance and should not treat the absence of reported exploitation in this material as proof that none has occurred.

Patch and Verify Deployments

Organizations should inventory NGINX deployments, compare installed versions with F5’s security guidance, and identify which systems have HTTP/2 enabled and are reachable from untrusted networks. They should apply the appropriate security update, then verify that the fixed version is running across production instances and any less visible environments, including staging or edge systems.

Where an update cannot be applied at once, Wiz recommends temporarily disabling HTTP/2 as a mitigation while teams test and schedule the patch. Administrators should check for further guidance from F5, including affected-version details and any updated indicators or remediation advice. The next key development is whether organizations report widespread exposure or exploitation; the supplied material does not confirm either.

Key Questions

What are the two NGINX vulnerabilities?

They are CVE-2026-123633 and CVE-2026-123007, two critical flaws that researchers say can permit unauthenticated remote code execution in affected NGINX deployments.

What condition does the report identify for exposure?

The report says HTTP/2 must be enabled on the affected NGINX server. Organizations should also check the relevant version and configuration against F5’s security advisory.

Has exploitation in the wild been confirmed?

The source material does not report confirmed attacks in the wild. It describes researchers’ testing and potential impact, but does not establish whether attackers have exploited the vulnerabilities.

What should NGINX administrators do?

Check F5’s advisory, identify affected and reachable deployments, and install the applicable security update. If an immediate upgrade is not possible, Wiz recommends temporarily disabling HTTP/2 while teams prepare the patch.

Source: wiz.io

You May Also Like

Is Wix Safe From Hackers

Discover how Wix defends against hackers and prioritizes security with advanced measures, ensuring a safe online experience for users.

Is Onedrive Safe From Hackers

Fend off hacker threats with Onedrive's advanced encryption and security measures, ensuring a safe environment for your data.

The Strange Weakness of “Trusted” Third-Party Integrations

The troubling vulnerabilities of “trusted” third-party integrations reveal hidden risks organizations must uncover before it’s too late.

What Makes AI-Generated Scams So Much Harder to Spot

Discover why AI-generated scams are increasingly difficult to detect and learn essential tips to protect yourself from evolving threats.