On 21 October 2026, the team behind PHP, the programming language that powers a huge share of the world’s websites, published emergency security releases. Two critical vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619 and nicknamed php2shell, allow unauthenticated remote code execution with a severity score of 9.2 out of 10. The same day, France’s CERT-FR updated its alert CERTFR-2026-ALE-014, and the French Interior Ministry took its exposed sites offline, including prefecture websites, at the request of ANSSI, the French national cybersecurity agency. Security agencies across Europe and the United States urged immediate patching, while mass exploitation attempts were reported worldwide. If you run a website, an online shop or a business application that serves users in France, or if your personal data sits on a server affected by this flaw, this article explains what happened, who is exposed, and what French law requires you to do now: notify, preserve evidence, file a complaint, and claim compensation.
I. An unprecedented PHP flaw forces France to pull government sites offline: what happened and who is exposed
A. What emergency patches did the PHP php2shell flaw trigger, and why did France take official action?
On 21 October 2026 at 14:00 UTC, the PHP project released four corrective versions, 8.5.12, 8.4.27, 8.3.36 and 8.2.35, fixing two vulnerabilities rated 9.2 on the CVSS v4.0 scale. According to the European Union Agency for Cybersecurity, these flaws can lead to remote code execution, and a demonstrated exploit shows that a single unauthenticated request can trigger the attack before any application code runs. Every installation that serves web requests is at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed, with the highest risk identified for mod_php configurations. Older branches such as PHP 8.1 and earlier no longer receive updates from the PHP project, which leaves them exposed unless a distributor or long-term-support vendor supplies a backported fix (CERT-EU Security Advisory 2026-018).
The American Cybersecurity and Infrastructure Security Agency confirmed the same analysis in its own words, urging organisations to patch immediately. It described the two flaws, CVE-2026-109618 and CVE-2026-109619, known as php2shell, as allowing unauthenticated remote code execution in PHP and affecting all PHP installations serving web requests, and it recommended updating without delay to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35. At the time of its publication, the agency stated that it had not observed exploitation, while underlining that unpatched systems remained at risk (CISA alert of 21 October 2026).
In France, the official reaction was unusually visible. The government computer emergency response team, CERT-FR, updated its alert CERTFR-2026-ALE-014 on the same day, and the Interior Ministry shut down its exposed sites, including those of prefectures. Technical reporting on the episode explains that the shutdown took place at the request of ANSSI and follows an instruction summarised as isolate then migrate: disconnect internet-facing resources from public networks until the fix is applied and verified (CERT-FR alert CERTFR-2026-ALE-014). The timeline published by the PHP Foundation adds an unsettling detail: the defect behind the first flaw had been identified as early as 2024 without a known exploitation vector, and researchers, some of them working with artificial intelligence models, demonstrated its severity within a few weeks during the summer of 2026.
International coverage described the scale of the threat in stark terms, with millions of exploitation attempts reported against websites around the world and several government services going dark as a precaution. In Ireland, website outages were widely reported in connection with the same flaw. In France, reporting at the time of writing described observed attack attempts with no intrusion publicly confirmed, which is reassuring but does not mean that exposed systems were not compromised silently. Remote code execution flaws are valuable precisely because a successful intrusion can leave few traces for the victim to notice.
Patch logistics matter as much as the patch itself. European guidance notes that Linux distributions and long-term-support vendors received the fixes in advance, so organisations should check with their vendor for updated packages rather than waiting for a routine update cycle. End-of-life versions require special attention: because the severity is so high, the PHP security team published minimal source backports for PHP 7.4, 8.0 and 8.1 for organisations that build from source or have no long-term-support vendor. Conversely, users of the volunteer-maintained remirepo repository were warned that it would have no updates on release day and should switch to distribution packages or build from source. Where immediate patching is genuinely impossible, the European advisory recommends isolating internet-facing resources from public networks until the fix is applied and verified, which mirrors the French isolate-then-migrate instruction. Temporary mitigations published for each vulnerability, such as adjusting memory limits, request sizes or session-upload settings, reduce exposure to specific attack paths but do not make an installation safe. Only the update fully fixes the flaws.
B. Who is exposed in France: operators, hosts and foreign businesses serving French users?
The circle of potentially affected organisations in France is very wide. Any company, association, local authority or public body whose website or online service runs on an unpatched PHP version is directly concerned, whether the server is managed internally, rented from a hosting provider or operated through a cloud platform. Online shops, booking platforms, customer portals, intranets exposed to partners, and mobile-application back ends are all within the scope if they serve web requests through PHP. Website owners who assume that their provider handles everything should check in writing which PHP version runs their service and whether the emergency patch has been applied, because contractual comfort is no substitute for technical verification.
Businesses running end-of-life versions face the greatest danger. Installations on PHP 8.1 or older receive no further updates from the PHP project, and the European advisory expressly warns that only distribution packages, long-term-support vendors or minimal source backports published for PHP 7.4, 8.0 and 8.1 can close the gap for organisations that build from source or lack vendor support. Many commercial and open-source products use PHP as a back-end technology without visibly exposing it, so an organisation can be vulnerable through a third-party application, a content management system, a customer relationship tool or an e-commerce module. The European advisory recommends checking inventories against published lists of third-party software embedding PHP, and French operators should extend that inventory exercise to every subcontractor with access to their systems.
Foreign businesses are concerned as soon as they serve users in France. A British, Irish or American company whose French-language shop, booking site or customer accounts run on vulnerable infrastructure faces the same French legal duties as a Paris company if personal data of people in France is compromised. Data protection duties follow the data, not the flag of the server. Employers with staff in France, schools and universities with student portals, health-sector publishers, and local authorities whose prefecture or municipal sites went offline as a precaution all belong to the exposed population. The French shutdown of prefecture sites is a clear signal: when the central state disconnects its own services rather than risk exploitation, no private operator should treat patching as routine maintenance to be scheduled next quarter.
Content management systems deserve particular vigilance. A large proportion of French showcase sites, blogs, association pages and small e-commerce shops run on PHP-based platforms whose core, themes and extensions each embed their own update cycle. An operator who updated the platform but left a plugin on an old branch, or who runs a custom module developed years ago, may remain exposed after a superficial update. Subcontractors multiply the risk: a web agency with privileged access, a freelance maintainer holding SSH keys, or a marketing tool connected to the customer database each widens the attack surface. French municipalities, hospitals, schools and mutual insurers that process sensitive data on PHP applications should treat this episode as a full-scale audit trigger, mapping every application, every version and every access right, because the sensitivity of the data they hold increases both the regulatory exposure and the scale of potential claims.
II. What French law requires after exposure to the flaw: notify, secure, complain and claim
A. How do you notify the CNIL, preserve evidence and file a criminal complaint in France?
The first duty after discovering a breach of personal data is notification. European data-protection law requires controllers to notify personal-data breaches to their supervisory authority, which in France is the CNIL, through its online breach-notification procedure. The CNIL explains that these duties, defined at Articles 33 and 34 of the GDPR, apply to every organisation that processes personal data once it becomes aware of a breach, and that notification depends on the risk the breach poses to the rights and freedoms of the individuals concerned (CNIL guidance on personal data breaches). Inside the supply chain, the duty is mirrored: processors that handle data on behalf of a controller must alert that controller of any security incident as swiftly as possible so it can meet its own obligations. A hosting provider or software maintainer that detects the intrusion must therefore warn its customer immediately, and the customer must in turn assess notification to the CNIL. Any delay in notifying must be explained, so every hour should be documented from the moment of discovery.
The notification itself must be substantive. The Regulation requires it to describe the nature of the breach, including where possible the categories and approximate number of data subjects and records concerned, to give the contact details of the data protection officer or another contact point, to describe the likely consequences, and to set out the measures taken or proposed to address the breach. Organisations operating in France that have not appointed a data protection officer should designate a single contact point now and prepare these elements in advance, because reconstructing them under pressure within a short statutory time frame is a frequent source of incomplete filings. Where the breach presents a high risk to individuals, those individuals must also be informed directly, and every communication should be kept consistent across the CNIL filing, customer messages and internal reports.
Notification does not replace investigation. Before rebuilding or reinstalling anything, preserve the evidence: server logs, firewall records, application traces, backup images and the exact versions in use. These elements establish when the system was exposed, whether data left the server, and which corrective measures were taken. They will support the CNIL file, the criminal complaint and any later insurance or liability claim. French law gives public services strong technical powers in this field: « Pour répondre à une attaque informatique qui vise les systèmes d’information affectant le potentiel de guerre ou économique, la sécurité ou la capacité de survie de la Nation, les services de l’Etat peuvent, dans les conditions fixées par le Premier ministre, procéder aux opérations techniques nécessaires à la caractérisation de l’attaque et à la neutralisation de ses effets en accédant aux systèmes d’information qui sont à l’origine de l’attaque. » (Article L2321-2 of the Code de la défense). Operators of vital importance and their subcontractors should therefore cooperate promptly with ANSSI and CERT-FR guidance, apply the isolate-then-migrate instruction where relevant, and keep written proof of every step.
Victims should also file a criminal complaint, because exploiting this flaw is a criminal offence under French law. « Le fait d’accéder ou de se maintenir, frauduleusement, dans tout ou partie d’un système de traitement automatisé de données est puni de trois ans d’emprisonnement et de 100 000 € d’amende. » (Article 323-1 of the Code pénal). Where the intrusion leads to data theft or alteration, the penalty rises: « Le fait d’introduire frauduleusement des données dans un système de traitement automatisé, d’extraire, de détenir, de reproduire, de transmettre, de supprimer ou de modifier frauduleusement les données qu’il contient est puni de cinq ans d’emprisonnement et de 150 000 € d’amende. » (Article 323-3 of the Code pénal). Both provisions carry seven years’ imprisonment and a 300,000 euro fine when committed against State-operated personal data systems, which covers attacks on the French public sites taken offline during this episode. French case law interprets unauthorised persistence on a system broadly. The Cour de cassation has held that « se rend coupable de l’infraction prévue par l’article 323-1 du code pénal celui qui se maintient dans un système de traitement automatisé de données en prenant connaissance du contenu des messages échangés au sein du réseau, à des fins étrangères à sa mission et à l’insu des titulaires des messages, même si, administrateur du réseau, il bénéficie, de par ses fonctions, d’un droit général d’accès à la messagerie. » (Cass. crim., 2 Sept. 2025, no. 24-83.605). A decade earlier, it had already confirmed a conviction where « M. X… s’est maintenu dans un système de traitement automatisé après avoir découvert que celui-ci était protégé et a soustrait des données qu’il a utilisées sans le consentement de leur propriétaire » (Cass. crim., 20 May 2015, no. 14-81.336). Anyone who probes, persists in or extracts data from a vulnerable French server therefore acts at their criminal peril, including security researchers who exceed an authorised scope.
Victims can report the facts to their local police or gendarmerie unit or directly to the public prosecutor, and join the criminal proceedings as civil parties to seek damages, which is exactly the path taken by the victim company in the September 2025 ruling discussed above (Cass. crim., 2 Sept. 2025, no. 24-83.605). A company established in Paris or elsewhere in Île-de-France can therefore file in the capital even if its servers sit in another region, and the complaint will be forwarded to the competent unit. In practice, cybercrime complaints from Paris are handled by specialised units and the cybercrime division of the Paris judicial court, and victims should attach their preserved logs, the CNIL notification receipt and a dated description of the patching timeline. Where the attackers are identified abroad, France can seek their surrender through extradition or European Arrest Warrant proceedings, a path described in detail in this analysis of French extradition procedure before the chambre de l’instruction.
B. Who pays for the damage: provider liability, customer claims and contracts under French law?
Civil liability in France starts from a simple principle: « Tout fait quelconque de l’homme, qui cause à autrui un dommage, oblige celui par la faute duquel il est arrivé à le réparer. » (Article 1240 of the Code civil). A company whose unpatched server leaks customer data, a host that ignores an emergency patch, or a maintenance provider that fails to monitor alerts can each face claims from victims who suffer loss, provided fault, damage and causation are established. Between contracting parties, the rule is equally direct: « Le débiteur est condamné, s’il y a lieu, au paiement de dommages et intérêts soit à raison de l’inexécution de l’obligation, soit à raison du retard dans l’exécution, s’il ne justifie pas que l’exécution a été empêchée par la force majeure. » (Article 1231-1 of the Code civil). A customer whose online shop stood offline for days, or whose client database was copied through php2shell, can therefore sue its provider for breach of the maintenance, hosting or security obligations in their contract.
Force majeure will rarely save a provider that simply failed to patch. French law defines it strictly: « Il y a force majeure en matière contractuelle lorsqu’un événement échappant au contrôle du débiteur, qui ne pouvait être raisonnablement prévu lors de la conclusion du contrat et dont les effets ne peuvent être évités par des mesures appropriées, empêche l’exécution de son obligation par le débiteur. » (Article 1218 of the Code civil). A critical flaw disclosed with same-day patches, an updated CERT-FR alert and coordinated warnings from European and American agencies is difficult to present as unforeseeable once the information is public, and its effects can be avoided by the appropriate measure, namely patching or isolating the system. Providers who can prove that they patched within hours, isolated exposed resources following ANSSI guidance and warned customers without delay will be in a far stronger position than those who waited. Limitation-of-liability clauses do not erase this analysis; they are interpreted strictly, they cannot cover wilful misconduct, and they never bind third-party victims who are not parties to the contract.
Individuals whose data was exposed have a direct European remedy that French courts apply every day. The Cour de cassation recalls that « toute personne ayant subi un dommage matériel ou moral du fait d’une violation du présent règlement a le droit d’obtenir du responsable du traitement ou du sous-traitant réparation du préjudice subi. » (Cass. soc., 24 June 2026, no. 24-22.792, citing Article 82(1) of the GDPR). The same decision, following the Court of Justice of the European Union, adds two practical clarifications: « la simple violation des dispositions de ce règlement ne suffit pas pour conférer un droit à réparation », so claimants must prove real material or moral damage, but no national rule may require that moral damage reach a certain seriousness threshold. In concrete terms, a person whose identity documents, health data or banking details leak through an unpatched French server can claim compensation for anxiety, loss of time, protective steps taken and any financial loss, without having to show that the distress crossed a severity threshold. Companies should therefore treat every exfiltrated record as a potential claim file.
Choosing where to sue favours victims in France. « Le demandeur peut saisir à son choix, outre la juridiction du lieu où demeure le défendeur : – en matière contractuelle, la juridiction du lieu de la livraison effective de la chose ou du lieu de l’exécution de la prestation de service ; – en matière délictuelle, la juridiction du lieu du fait dommageable ou celle dans le ressort de laquelle le dommage a été subi » (Article 46 of the Code de procédure civile). A customer domiciled in Paris or elsewhere in Île-de-France who suffers the consequences of a breach there can bring the case before the courts of that place, including the Paris judicial court, even if the provider or host is established abroad. This is decisive for foreign operators: serving French customers means accepting the jurisdiction of French courts for damage suffered in France. Practical steps for claimants include having the exposure formally recorded by a commissaire de justice, keeping every notification and invoice, declaring the incident to cyber-insurance carriers under the policy’s own notice terms, and auditing contracts now, before the next emergency patch, to clarify who patches, who monitors alerts, who notifies the CNIL and who bears the cost of downtime.
Contract review should start today, not after the next incident. Identify who is contractually responsible for monitoring security alerts such as CERT-FR publications, who applies patches and within what time, who decides to isolate or shut down a service, who notifies the CNIL and affected individuals, and who bears the cost of downtime, forensic investigation and customer communication. Service-level clauses promising availability percentages sit uneasily beside emergency shutdowns ordered for security reasons, so the contract should expressly allow precautionary isolation. Cyber-insurance policies should be re-read with the same attention: notice conditions, panel requirements for forensic experts and lawyers, and exclusions for unpatched or end-of-life software can determine whether the insurer responds. An insurer that discovers a server still running an unsupported PHP version months after this episode may dispute coverage, which is one more reason to document the patching date and keep vendor confirmations.
Conclusion
The php2shell episode is a stress test for every organisation operating online in France. The French state itself disconnected prefecture and ministerial sites rather than leave them exposed, European and American agencies published aligned emergency guidance, and mass exploitation attempts were reported within hours of disclosure. Against that background, French law leaves little room for passivity: breaches of personal data must be notified to the CNIL, evidence must be preserved, criminal complaints can and should be filed, and both providers and controllers face civil claims where fault and damage are shown. Force majeure will protect only those who reacted as diligent professionals, and data subjects need prove only real damage, not dramatic damage, to obtain compensation. Patch now, document everything, and review who in your contracts owns each security duty before the next critical alert arrives.