20 November 2026 · Guidance
CSSF Says NGINX Remote Code Execution Is a Major ICT Incident to Notify
On 20 November 2026 the CSSF warned supervised entities about five NGINX vulnerabilities (NGINX2ROOT). Unauthenticated remote code execution through them counts as a major ICT-related incident to notify under Circular CSSF 25/893 (DORA) or Circular CSSF 24/847.
What happened
On 20 November 2026 the CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission) published a communiqué on NGINX2ROOT, five vulnerabilities in NGINX (CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810 and CVE-2026-113425). Under exploitable conditions they let an unauthenticated remote attacker run code with the privileges of an NGINX worker process, which can lead to compromise of the web server and, in some configurations, the host. The CSSF points to the report of CIRCLComputer Incident Response Center Luxembourg and its recommendations.
What it changes
The CSSF reminds all supervised entities that unauthenticated remote code execution is unauthorised malicious access, so it constitutes a major ICT-related incidentAn ICT-related incident with a high adverse impact on the network and information systems that support critical or important functions of a financial entity. Financial entities must report it to their competent authority in initial, intermediate and final reports. that must be notified. Entities notify under Circular CSSF 25/893 (DORADigital Operational Resilience Act) or Circular CSSF 24/847, depending on their type. The CSSF took the same position on PHP in October and on Java4Shell on 18 November.
Who is affected
The communiqué lists, among others, credit institutions, investment firms, payment and e-money institutions, central securities depositories, crypto-asset service providers, investment fund managers and crowdfunding service providers. It matters to those that run NGINX directly or through ICT third-party providers.
What to do now
- Identify NGINX instances, including reverse proxies and those run by ICT third-party providers.
- Apply the fixes or mitigations in the CIRCL report and check logs for signs of exploitation.
- If exploitation is confirmed, classify and notify it as a major ICT-related incident under the circular that applies to you.
Incident Reporting Desk
Our Incident Reporting Desk classifies a confirmed exploitation against the DORA criteria and prepares the notification to the CSSF with you. Our DORA Compliance Audit checks that your incident classification and reporting process holds up.
