Regulatory Updates
Bills, adoptions, entry into force, guidance and deadlines, checked against the official sources.
Updates
20 November 2026GuidanceLuxembourg
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.
18 November 2026GuidanceLuxembourg
CSSF Says Java4Shell Remote Code Execution Is a Major ICT Incident to Notify
On 18 November 2026 the CSSF warned supervised entities about Java4Shell (CVE-2026-114938) in the OpenJDK Base64 decoder. Unauthenticated remote code execution through it counts as a major ICT-related incident to notify under Circular CSSF 25/893 (DORA) or Circular CSSF 24/847.
21 October 2026GuidanceLuxembourg
CSSF Says PHP Remote Code Execution Is a Major ICT Incident That Must Be Notified
The CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission) told supervised entities on 21 October 2026 that unauthenticated remote code execution through two PHP flaws is a major ICT-related incident to notify. Entities should treat all PHP-powered services as potentially exposed until affected versions are confirmed.
2 October 2026GuidanceLuxembourg
CSSF Says DORA Applies to Control Agents of Tokenised Funds
The CSSF says control agents of tokenised funds are subject to DORA for that activity, which is highly likely a critical or important function. ICT third-party arrangements supporting it must be notified under Circular CSSF 25/882.
29 September 2026GuidanceLuxembourg
CSSF Sets Out What It Expects in DORA Major ICT Incident Reports
On 29 September the CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission) published its own operational instructions on DORADigital Operational Resilience Act 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. reports and asked financial entities to apply the ESAsEuropean Supervisory Authority' instructions too. They cover incident descriptions, reclassification, root causes and the final report's action plan.
28 September 2026GuidanceLuxembourg
Luxembourg’s NIS2 Authorities Publish Joint Rulebooks for Handling Cyber Incidents
The HCPN, GOVCERT.LU, CIRCL, the CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission) and the ILR published nine incident-handling rulebooks on 28 September under Article 14(5) of Luxembourg's NIS2Directive on Measures for a High Common Level of Cybersecurity Across the Union law. They give practical steps for entities after a significant incidentUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident.. They are guidance and do not set legal duties.
27 August 2026GuidanceLuxembourg
CSSF Moves Third-Country Branches in Luxembourg Under Its DORA Circulars
CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission) Circular 26/915 applies with immediate effect. Qualifying third-country branches in Luxembourg leave Circular 20/750 and Part II of 22/806 and fall under the DORADigital Operational Resilience Act circulars on ICTInformation and Communication Technology third parties, incident costs and incident reporting.