Plan ahead Medium Patch available CVSS 8.1 (NVD)
Decade-old NGINX HTTP/2 flaw allows remote code execution without login
The Hacker NewsNGINX, F5CVE-2026-123007
What happened. A flaw in NGINX's HTTP/2 support, CVE-2026-123007 ("nginx2root"), lets an attacker run code on servers with HTTP/2 enabled without logging in. It has been present since version 1.9.5, released in September 2015. F5 released fixed versions 1.31.9 and 1.30.7.
Who is affected. Servers running open-source NGINX from version 1.9.5 with HTTP/2 enabled. Industrial sites using NGINX in portals or remote-access gateways may be exposed.
What to do. Check whether you run NGINX with HTTP/2 enabled, then update to fixed version 1.31.9 or 1.30.7.
Why it matters to your site. NGINX is a common web server in plant portals, remote access gateways and vendor systems, so unauthenticated code execution there is a risk for industrial networks.
When to act. Plan ahead: Not an industrial-specific item; patch in normal cycles unless NGINX fronts plant services.
Editor's reading
Forasset ownerIT security
- Purdue level
- L4
- L3.5
Why: NGINX often runs web portals and gateways at the boundary between the plant and business networks (L3.5 and L4), which the source does not name specifically.
- Are you exposed?
Look in your server and application inventory for NGINX from 1.9.5 onwards, and check the configuration for HTTP/2 being enabled.
- If you cannot fix it yet
- Disable HTTP/2 on NGINX servers that cannot be updated yet.
- Keep NGINX servers that are reachable from outside off the plant network until patched.
- Watch for
- Unusual or malformed HTTP/2 requests to NGINX servers from unknown sources.
- Unexpected processes or outbound connections started from the NGINX server.
- ATT&CK for ICS
- T0866Exploitation of Remote Services
Inferred from the facts above, not stated by the source. Check it against your own site before acting.
Source: The Hacker News (opens thehackernews.com)
Published by Industrial Cyber Brief · Editor: Abhinav Roy · Drafted by AI and checked by code: how this is made · Corrections
More on F5 CVE-2026-123007