Critical PHP flaws: Luxembourg's CERC and the CNPD urge patching after the fixes of 21 October 2026
Luxembourg's CERC and the CNPD urge organisations to patch two critical PHP flaws, CVE-2026-109618 and CVE-2026-109619, fixed on 21 October 2026.
Key takeaways
- On 21 October 2026 the PHP project released PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 to fix CVE-2026-109618 and CVE-2026-109619, two flaws rated CVSS v4.0 9.2 that can allow unauthenticated remote code execution.
- Luxembourg's cyber risk assessment cell (CERC), with HCPN/GOVCERT, the ILR, the CSSF, the CTIE and CIRCL taking part, met on 21 October 2026 and recommended applying the patches as soon as possible.
- On 30 October 2026 the CERC reported that, after a further meeting on 28 October, no confirmed malicious exploitation attempt and no confirmed compromise linked to the two flaws had been observed; the situation remains under monitoring.
- On 22 October 2026 the CNPD said a vulnerability alone is not a personal data breach, but a resulting incident may have to be notified within 72 hours under Article 33 GDPR.
- According to CIRCL and the PHP project, updating is the only complete mitigation; PHP 8.1 and older no longer receive regular updates.
Luxembourg’s authorities are telling every organisation that runs PHP to update now. On 21 October 2026 the PHP project released fixes for two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, which can allow unauthenticated remote code execution. The national cyber risk assessment cell (CERC) recommended applying them as soon as possible, and on 22 October the CNPD reminded organisations of their GDPR breach-notification duties.
Update: no confirmed incident as of 30 October 2026
After a further meeting on 28 October, the CERC said on 30 October that the authorities had observed neither a confirmed malicious exploitation attempt nor a confirmed compromise linked to the two flaws. It credits the prompt application of security patches with significantly reducing the risk, and notes that GOVCERT had relayed the recommendations to critical entities. The communiqué also lists Restena and the State Intelligence Service (SRE) among the participating bodies, in addition to those named below. The situation remains under monitoring, and the CERC asks organisations to stay vigilant and keep applying security updates.
No confirmed incident is not the same as no exposure. An unpatched server is as vulnerable today as it was on 21 October.
What happened
On 20 October the PHP project announced a security release for two critical vulnerabilities, both rated CVSS v4.0 9.2. The advisory of 21 October lists the fixed versions: PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. The highest risk is with Apache mod_php, where a demonstrated exploit lets an unauthenticated request trigger the attack before any application code runs.
CIRCL’s report TR-102 considers every PHP installation that serves web requests potentially at risk, including PHP-FPM, php-cgi, FrankenPHP and LiteSpeed. It documents validated exploit demonstrations, not evidence of widespread exploitation, and notes that reports of suspicious activity preceded the release.
The CERC, with HCPN/GOVCERT, the ILR, the CSSF, the CTIE, CIRCL, the Luxembourg Army and the CGIE around the table, met on 21 October after the early disclosure, and again once the patches were out. The CTIE temporarily made certain of its services unavailable as a precaution, and the Luxembourg CSIRTs contacted the entities in their communities.
| Source | Date | Key message |
|---|---|---|
| PHP project | 21 October 2026 | Update to 8.5.12, 8.4.27, 8.3.36 or 8.2.35; no complete mitigation exists |
| CERC | 21–22 October 2026 | Patch as soon as possible; otherwise risk analysis, compensating measures or temporary shutdown; check for compromise |
| CIRCL (TR-102) | 21 October 2026 | Patch, restart all PHP workers, do not rely on the version string alone |
| CNPD | 22 October 2026 | Check providers and hosts; assess GDPR Articles 33 and 34 if personal data is affected |
| CERC | 30 October 2026 | No confirmed exploitation attempt or compromise so far; stay vigilant |
Why it matters
Can you name, today, every server in your organisation that runs PHP, including those your web agency or hosting provider manages? If the answer takes a week, so does your exposure.
PHP sits under many websites, content management systems, customer portals and intranets. Sometimes nobody inside the organisation chose it: a supplier did. A patch you cannot locate is a patch you cannot apply.
The good news: fixes exist for every supported branch, and the steps are short. The CNPD also draws a useful line. A vulnerability alone is not a personal data breach. An incident that exposes, alters or destroys personal data is, and Article 33 GDPR then gives you 72 hours, where possible, to notify. Entities under the Luxembourg NIS2 law also have incident notification duties towards their authority; the ILR receives notifications through its SERIMA platform.
What to do now
- List every system running PHP, Internet-facing ones first, and ask your hosting provider and web agency to confirm in writing when they patched.
- Update to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, restart all PHP workers and check that the patched runtime actually serves requests. Distributions may backport fixes, so do not judge by the version string alone.
- If you cannot patch at once, document a risk analysis, apply the interim settings listed by PHP and CIRCL, and consider taking exposed systems offline.
- Look for signs of compromise. If personal data was affected, assess the 72-hour notification under Article 33 GDPR and document the incident either way; financial entities should also check the CSSF’s DORA incident reporting instructions.
- Plan the upgrade of anything on PHP 8.1 or older. PHP 8.2 receives security fixes only until 31 December 2026.
Questions & answers
Which PHP versions fix CVE-2026-109618 and CVE-2026-109619?
PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, all released on 21 October 2026. For PHP 7.4, 8.0 and 8.1 the PHP security team only published minimal source backports, which are not a return to regular support.
Must organisations notify the CNPD about the PHP vulnerability?
Not for the vulnerability alone. If exploitation led to unauthorised access to, or loss, alteration or destruction of, personal data, the controller must assess Articles 33 and 34 GDPR: notification within 72 hours where possible, unless the breach is unlikely to result in a risk to individuals.
Are the PHP vulnerabilities being exploited?
According to CIRCL's report TR-102 of 21 October 2026, the advisories document validated exploit demonstrations, which are not evidence of widespread exploitation in the wild. Reports of suspicious activity preceded the official release. On 30 October 2026 the CERC said the authorities had so far observed no confirmed malicious exploitation attempt and no confirmed compromise.
How long will PHP 8.2 receive security fixes?
Until 31 December 2026, according to the PHP project. After that date it receives no further security fixes.
Sources
- La CERC salue la réactivité des organisations face aux vulnérabilités critiques de PHP : aucun incident confirmé à ce jour (30 October 2026) · gouvernement.lu
- Réunion de la cellule d'évaluation du risque cyber (CERC) – Recommandations aux organisations utilisant PHP (22 October 2026) · gouvernement.lu
- Réunion d'une Cellule d'évaluation du risque cyber (21 October 2026) · gouvernement.lu
- Vulnérabilités critiques affectant PHP (22 October 2026) · CNPD
- TR-102 – PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 · CIRCL
- Security advisory: critical remote code execution vulnerabilities, update now (21 October 2026) · PHP
- NIS 2 · ILR
Written and fact-checked against primary sources.