Live Updates

Critical security vulnerabilities in NGINX (NGINX2ROOT)

AI Analysis

CSSF has warned supervised entities about five NGINX2ROOT vulnerabilities that may enable unauthenticated remote code execution with the privileges of an NGINX worker and, in some configurations, compromise of the host. The vulnerabilities affect distinct configurations including HTTP/2, HTTP/3, reverse proxying, runtime DNS resolution and NGINX mail proxy authentication; independent security analysis reports patched NGINX versions 1.30.7 and 1.31.9, a public proof of concept for at least one flaw, and no confirmed widespread exploitation as of 20 November 2026.

Key dates

2026-11-18
CIRCL published TR-105 on NGINX2ROOT, and independent technical reporting indicates that NGINX released fixes including stable 1.30.7 and mainline 1.31.9.
2026-11-20
CSSF published its communiqué warning supervised entities about the five vulnerabilities and reminding them that unauthorised remote code execution is a major ICT-related incident requiring notification under CSSF Circular 25/893 or CSSF Circular 24/847, as applicable.

Suggested considerations

  • Firms should inventory internet-facing and internal NGINX deployments, including embedded products, containers, Kubernetes ingress controllers, appliances and vendor-managed services, and map each deployment to the five CVEs and the relevant enabled features.
  • Technology and security teams may wish to prioritise upgrades to NGINX Open Source 1.30.7 or later stable releases, NGINX Open Source 1.31.9 or later mainline releases, or the corresponding supported NGINX Plus fixes, subject to vendor compatibility and change-control requirements.
  • Where immediate patching is not feasible, firms should consider temporary risk reduction such as restricting exposure, disabling unnecessary HTTP/2, HTTP/3, mail proxy and vulnerable proxy or resolver configurations, while recognising that feature disabling is not a universal mitigation.
  • Firms should validate remediation through service restarts, version and package verification, configuration review and appropriate security testing rather than relying only on version banners; independent commentary reports reproducible testing for several attack paths and a public proof of concept for CVE-2026-123007.
  • Compliance teams may wish to assess whether exploitation, attempted exploitation, or unauthorised remote code execution has occurred and preserve relevant logs, endpoint evidence, cloud records and incident timelines.
  • Entities subject to CSSF Circular 25/893 should consider assessing and notifying the incident under the DORA major ICT-related incident framework; entities outside the applicable DORA scope should assess notification under CSSF Circular 24/847, using the relevant regulatory classification and reporting channels.
  • Firms should document affected assets, exposure, compensating controls, patch decisions, management escalation, third-party dependencies and the rationale for any delayed remediation for operational-resilience and supervisory-review purposes.

What changed

The 20 November 2026 CSSF communiqué does not introduce a new technical rule or universal patch deadline, but it formally alerts supervised entities to CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425 and strongly recommends that affected entities consider the CIRCL TR-105 report and take appropriate action. CSSF states that unauthorised remote code execution through these vulnerabilities constitutes a major ICT-related incident requiring notification under CSSF Circular 25/893 for entities within the DORA framework or CSSF Circular 24/847 for entities to which that regime applies, depending on the entity type. Independent technical commentary identifies NGINX Open Source 1.30.7 and 1.31.9 as the relevant patched stable and mainline releases, respectiv

Compliance impact

The principal impact is a high-severity operational-resilience and cyber-risk issue involving potentially unauthenticated remote code execution, web-server compromise and, in certain configurations, underlying-host compromise. CSSF expressly links the event to major ICT-related incident notification obligations, so firms should treat confirmed exploitation or qualifying unauthorised access as pote

Who is affected

  • Luxembourg credit institutions and other financial entities within the scope of DORA and CSSF Circular 25/893 that operate or depend on affected NGINX services
  • Luxembourg investment firms, investment fund managers and other CSSF-supervised entities subject to CSSF Circular 24/847 where the applicable ICT incident-reporting regime is not DORA
  • Entities operating internet-reachable NGINX Open Source, NGINX Plus, embedded NGINX appliances, ingress controllers or other products containing affected NGINX versions
  • Entities using affected configurations including HTTP/2, HTTP/3 or QUIC, upstream proxying, request-derived proxy_pass with runtime DNS resolution and subrequests, or NGINX mail proxy authentication
  • Digital Operational Resilience Act (Regulation (EU) 2022/2554)
  • CSSF Circular 25/893
  • CSSF Circular 24/847

AI-generated analysis. May contain errors or omissions — verify with the original CSSF source before acting. Full disclaimer.

What the CSSF said

CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425

Published by CSSF . Read the full notice at the source for the authoritative text.

Sectors

View Original on CSSF Back to Feed

Share this update