---
title: "CSSF Says PHP Remote Code Execution Is a Major ICT Incident That Must Be Notified"
url: "https://grc.plus/updates/cssf-php-remote-code-execution-major-ict-incident/"
type: "Update"
updated: "2026-11-13"
publisher: "GRC+"
---

# CSSF Says PHP Remote Code Execution Is a Major ICT Incident That Must Be Notified

## What happened

The CSSF issued a [communiqué on 21 October 2026](https://www.cssf.lu/en/2026/10/critical-security-vulnerabilities-in-php/) 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 CSSF 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 (DORA) 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 providers, investment fund managers, central securities depositories and other supervised types.

## What to do now

- Inventory every PHP-powered service, including those run by ICT 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 CSSF‘s position.
- If you are unsure whether your facts trigger notification, ask the CSSF.

Principal Consultant

## [Ahmet Ucar](https://grc.plus/consultant/ahmet-ucar/)

Helps clients comply with their regulatory requirements with a plan their board can approve.

[Book a 30-Minute Call](https://meetings-eu1.hubspot.com/ahmet-ucar)
