21 October 2026 · Guidance
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.
What happened
The CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission) issued a communiqué on 21 October 2026 on CVE-2026-109618 and CVE-2026-109619 in the PHP runtime. Both can lead to unauthenticated remote code execution. When it published, the affected versions were not yet confirmed.
What it changes
The CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission) reminds supervised entities that this remote code execution “consists of an unauthorised malicious access” and so “constitutes a major ICT-related incident that needs to be notified”. The route is Circular CSSF 25/893 (DORADigital Operational Resilience Act) or CSSF 24/847, depending on the type of entity. The notice does not say whether exposure alone triggers this, or only exploitation. It sets no new rule, and it strongly recommends acting on a report from CIRCL, which we did not read.
Who is affected
The notice lists credit institutions, investment firms, payment and e-money institutions, crypto-asset service providersA legal person or other undertaking that provides one or more crypto-asset services, such as custody, exchange, trading platforms, transfers or advice, to clients on a professional basis, and is allowed to do so under MiCA. Authorised providers can passport their services across the EU and are in scope of DORA., investment fund managers, central securities depositories and other supervised types.
What to do now
- Inventory every PHP-powered service, including those run by ICTInformation and Communication Technology third parties.
- Read the CIRCL report and apply its recommendations.
- Check logs for signs of exploitation and record the result.
- Decide which circular applies to you, and brief your incident team on the CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission)‘s position.
- If you are unsure whether your facts trigger notification, ask the CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission).
Incident Response Plan and Exercise
We inventory your PHP services, review the logs and run the notification decision with your incident team. Our DORADigital Operational Resilience Act audit then checks that your classification and reporting procedures match what the CSSFCommission de Surveillance du Secteur Financier (Financial Sector Supervisory Commission) expects.
