Cybersecurity Authority warns of risk of websites being taken offline

National Cybersecurity Authority warns of two critical NGINX vulnerabilities. The flaws affect HTTP/2 and could cause websites to go offline or allow malicious code to be executed.

Cybersecurity Authority warns of risk of websites being taken offline

This article is an AI translation of an original piece published in Greek. Read original

The National Cybersecurity Authority (EAK) has issued a warning about two critical security vulnerabilities in widely used NGINX software that could put the availability and security of websites and online applications at risk.

The flaws could allow malicious third parties to take a website offline or, in certain circumstances, execute malicious code on the server hosting it, without first having to authenticate. The Authority recommends immediately applying the available security updates, prioritising affected servers that are accessible from the internet.

In detail, the vulnerabilities, identified as CVE-2026-123007 and CVE-2026-123633, concern the way NGINX handles connections using the HTTP/2 protocol. Under certain conditions, a remote attacker could cause an outage or execute code with the privileges of the NGINX process, without first having to authenticate. If the same server hosts multiple websites or applications, the impact could extend to more than one digital service.

What the vulnerabilities affect

The first vulnerability affects NGINX installations that accept HTTP/2 connections, even when they serve only static content. The second affects installations that also forward requests to other servers.

Researchers have already demonstrated a successful exploit of the first vulnerability. According to a CERT-EU advisory dated 18 November 2026, no exploitation in real-world attacks had been reported by the time it was published.

The EAK recommends that public bodies, businesses, hosting providers and IT system administrators identify affected systems. They should record the use of NGINX Open Source and NGINX Plus, including deployments in container environments, Kubernetes and third-party products. Where a content delivery network (CDN) is used, they should check whether NGINX itself accepts HTTP/2 connections and whether it is directly accessible from the internet.

Updates should also be installed immediately. Fixed versions of NGINX Open Source are available: 1.30.7 (stable) and 1.31.9 (mainline). For NGINX Plus, Linux distribution packages and products incorporating NGINX, administrators should apply the relevant vendor’s update and confirm that the fixed version is running.

If an update cannot be applied immediately, the Authority recommends temporarily limiting exposure by disabling HTTP/2 on affected installations, after checking the impact on services that require it, such as gRPC. This measure addresses the two specific vulnerabilities.

Finally, administrators should check for signs of exploitation. They should examine logs for repeated, unexpected termination of NGINX processes, particularly if it coincides with unusual processes starting on the same server.

v
Privacy