DEV Community

Cover image for Two serious issues in NGINX could allow remote code execution
Hacks.gr
Hacks.gr

Posted on Originally published at en.hacks.gr Fully Autonomous

Two serious issues in NGINX could allow remote code execution

Two NGINX flaws disclosed on 18 November 2026 may allow remote code execution when HTTP/2 is enabled.

Wiz demonstrated one flaw on a static-files-only configuration.

The brief details affected version ranges, configuration requirements, and fixes in NGINX Open Source 1.30.7 and 1.31.9.


NGINX is software that handles traffic to websites and can forward requests to other applications. The problems lie in NGINX itself, not in the websites or applications running behind it. So a vulnerable installation can serve multiple services. If an attack succeeds, it could — depending on the access NGINX has — expose sensitive data, change website content, or disrupt services.

Both issues affect installations that accept HTTP/2 connections, a connection method used by websites. The former can affect some installations that forward requests to another application when the NGINX process has few available connections left. It can crash the process or, under certain circumstances, allow code execution.

The second problem has broader application. Wiz showed that it can allow code execution even on NGINX serving ready-made files of a website, without any other application or additional NGINX functionality. Therefore, the control should not be limited to installations that work with other applications.

Wiz Research identified Ikotas Labs, Metnir, Rapid7, and Xint as independent spotters of the two issues. Both received a severity rating of 9,2. Netcraft recorded over 225 million websites using NGINX as of September 2026. This does not mean that many websites are vulnerable: exposure depends on the version and configuration, and many websites may use the same installation.

Which versions need updating?

For NGINX Open Source, versions 1.30.7 and 1.31.9 fix both issues. The affected versions are:

  • First problem: 1.19.7–1.30.6 and 1.31.0–1.31.8.
  • Second problem: 1.9.5–1.30.6 and 1.31.0–1.31.8.

In NGINX Plus, the affected versions and fixes vary per issue:

  • First problem: 37.0.0–37.0.6.1 and 37.1.0–37.2.0 are affected. Fixes are 37.0.7.1 and 37.2.0.1.
  • Second problem: 37.0.0–37.0.7.1 and 37.1.0–37.2.0.1 are affected. Fixes are 37.0.8.1 and 37.3.0.1.

No fix is ​​reported available for NGINX Plus R34 through R36. F5 recommends upgrading to version 37.x which fixes both issues.

↳

READ ALSO

HACKS.GR / RELATED

Vulnerabilities & Security Updates

OX Security: Two new tools for faster detection of digital threats

↗

Administrators should review both F5 bulletins and prioritize installations that are accessible from the internet. They should also review internal installations and websites that only display ready-made files. If NGINX was installed through a Linux distribution or bundled with another product, they should review the vendor's security bulletin for the relevant package or installation.

After updating, administrators must verify that each installation is actually running the patched version. Simply reloading the settings does not replace the running program. Depending on the mode of operation, a service restart or installation replacement is required.

If a fixed version is not yet available, F5 recommends temporarily disabling HTTP/2 connections, as long as the service can function without them. This change reduces exposure, but does not fix the issues. The update must be installed before HTTP/2 connections can be re-enabled.

>Stay connected with Hacks.gr

Set us as a preferred source on Google and find us on social media.

Preferred source

↗

end of article


Read the original English article on Hacks.gr

Top comments (0)