Critical PHP Flaws Force European Government Websites Offline: CVE-2026-109618 & CVE-2026-109619

Government and university websites across Finland, the Netherlands, and Austria have been taken offline following the disclosure of two critical remote code execution (RCE) vulnerabilities in PHP. While emergency security patches (versions 8.5.12 to 8.2.35) were released on 21 October 2026, many public institutions face severe disruptions due to reliance on legacy, unsupported PHP versions.
The vulnerabilities, CVE-2026-109618 and CVE-2026-109619, carry severity scores of 9.2 under CVSS version 4.0. Both can allow attackers to execute code remotely without authentication. That makes them particularly dangerous on servers accessible from the public internet, where a successful attack may require neither stolen credentials nor an existing foothold.
The scale of the potential exposure is considerable. PHP is used by approximately 69.3% of websites whose server-side programming language is known. Researchers Silas Cutler and Henk Poley have estimated that between 1.3 million and 1.9 million internet-exposed hosts run PHP, although that figure should not be confused with the number confirmed vulnerable to these particular flaws.
For European public authorities, the immediate question was whether to keep essential digital services available while security teams assessed the threat. Several decided that temporary disruption was preferable.
Governments Choose Downtime Over Uncertain Exposure
Finland's central government service provider, Valtori, suspended public web services as the vulnerabilities attracted attention. In the Netherlands, websites belonging to the lower house of parliament, the National Cyber Security Centre and the National Institute for Public Health and the Environment were temporarily taken offline. Municipal portals were also affected.
Austria experienced similar disruption. The University of Vienna disabled its websites, webmail and Moodle learning platforms, extending the consequences beyond public information pages to services used for everyday academic work.
These decisions were taken before evidence emerged of widespread successful compromises of government systems. They were precautionary, prompted by the seriousness of the vulnerabilities and indications that attackers had already begun testing ways to exploit them.
The distinction matters. Taking a website offline does not establish that it has been breached. In this case, the shutdowns illustrate how public institutions are beginning to respond to serious cyber threats even when the extent of an attack remains uncertain.
Keeping a potentially exposed service running preserves access for citizens, students and staff. Disconnecting it removes that immediate risk but interrupts the work the service was designed to support. Neither option is cost-free.
For institutions responsible for sensitive public services, the calculation increasingly favours containment when reliable protection cannot be established quickly.
A Security Crisis Built Into the Software Stack
The PHP vulnerabilities differ from security problems confined to a particular website or third-party extension. They affect the underlying runtime used to execute applications.
That distinction gives the incident its wider significance.
WordPress, Drupal, Joomla, Magento and Laravel all operate within the PHP ecosystem. Their use spans government portals, online shops, educational platforms and business applications. A vulnerability in the language's core can therefore create exposure across otherwise unrelated organisations.
An administrator may have maintained a content management system carefully, installed its security updates and restricted access to sensitive functions, yet still face a serious problem if the underlying PHP installation is vulnerable.
The speed of the disclosure compounded the difficulty.
Details of the two flaws began circulating on Hacker News and social media on 20 October. A demonstration exploit chain known as php2shell, associated with researchers LCFR, Calif.io and Kirill Firsov, also surfaced. The PHP security team responded with advance notice of an emergency release.
Cloudflare's chief technology officer, Dane Knecht, reported that the company had observed early attacks. Cloudflare deployed temporary web application firewall rules for customers while developers prepared permanent fixes.
By 21 October, organisations were confronting a threat that had moved rapidly from public discussion to attempted exploitation.
There was little opportunity for a conventional maintenance cycle.
The PHP security team released emergency updates at 14:00 UTC on 21 October, providing corrected versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
For administrators operating supported software, the response was demanding but relatively straightforward: identify affected installations, apply the relevant update, test applications, and restore services where necessary.
For those operating older systems, the situation was substantially more complicated.
The Divide Between Supported and Abandoned Systems
PHP 8.1 and earlier branches are outside official security support and received no patches in the emergency release.
This creates two different categories of risk within the same software ecosystem.
An organisation running a maintained PHP version can obtain a vendor-supported correction. One relying on an obsolete branch must consider upgrading the runtime, developing or obtaining a separately maintained fix, or isolating the affected service.
Each alternative carries operational consequences.
Older applications may depend on language behaviour, extensions or frameworks that are incompatible with current PHP releases. Upgrading the runtime can require substantial code changes and testing. Attempting to backport security corrections introduces its own technical risks, particularly where the original application has received little maintenance.
Isolation, meanwhile, can mean withdrawing a service from public access indefinitely.
The problem is particularly acute for organisations that have kept older applications running because they continue to perform a necessary function. Software can remain useful long after its security support has ended. The vulnerability does not become less serious because replacing that software is expensive.
The PHP developers have also ruled out a seemingly convenient alternative. Standard configuration changes, including disabling session upload progress, do not protect installations against these flaws.
Administrators cannot rely on a simple settings adjustment to avoid the underlying problem.
Web application firewalls can help reduce exposure while patches are deployed, but their emergency rules are temporary defences rather than substitutes for correcting the vulnerable runtime. Cloudflare's rapid intervention illustrates the value of such services, while also showing the limits of depending on protection outside the affected software itself.
Why Earlier Warnings Were Not Enough
PHP has faced serious exploitation risks before.
CVE-2024-4577, a PHP-CGI argument injection vulnerability, was added to the US Cybersecurity and Infrastructure Security Agency's Known Exploited Vulnerabilities catalogue in 2024. Another remote code execution vulnerability, CVE-2019-11043, affected PHP-FPM configurations involving Nginx and was added to the catalogue in 2022.
Both cases showed how weaknesses in the components responsible for running web applications could become attractive targets for attackers.
The latest incident raises a related but broader question about how organisations manage the software beneath their visible applications.
Cybersecurity programmes often concentrate on the applications users interact with, the services exposed to the internet and the controls placed around them. Yet effective protection also depends on knowing precisely which runtime versions those applications use.
That information is not always readily available across complex hosting environments.
The emergency has strengthened the case for automated asset discovery, continuous vulnerability management and more rigorous software bills of materials. Such measures allow organisations to identify dependencies before an urgent security advisory forces them to reconstruct their infrastructure under pressure.
For hosting providers, the challenge extends across customer environments. Updating a shared runtime may protect numerous services, but compatibility requirements can complicate deployment. Leaving older installations untouched, however, prolongs the exposure.
The issue is therefore not simply whether a patch exists. It is whether organisations know where it must be applied and can deploy it without causing unacceptable disruption.
Europe’s Cybersecurity Response Faces a Practical Test
CERT-EU's advisory 2026-018 warned that PHP versions dating back to PHP 5 could potentially be affected. The UK's National Cyber Security Centre and its Dutch counterpart also urged organisations to update vulnerable installations or temporarily isolate exposed applications.
Their warnings arrived as exploitation attempts were already being observed, although confirmed mass-scale breaches of state systems had not been established.
The coordinated response illustrates the importance of rapid intelligence sharing between European cybersecurity authorities. But issuing guidance is only the beginning. National agencies can warn of a vulnerability; they cannot instantly modernise the applications operated by every public institution, university, municipality or business.
That responsibility remains with the organisations maintaining the systems.
Security teams must establish which services are exposed, determine their PHP versions, deploy the appropriate fixes and verify that applications continue to operate correctly. Unsupported installations require more difficult decisions about migration or isolation.
The emergency also changes the meaning of service availability for public-sector technology managers.
A government website that remains online during an active security threat may appear reliable to its users while exposing the institution to a much greater interruption later. Taking it offline protects the underlying environment but immediately denies access to the public.
The shutdowns in Finland and the Netherlands show that some authorities are prepared to accept the second outcome rather than gamble on the first.
That approach may become harder to avoid as public services grow more dependent on software whose maintenance cycles do not match the lifespan of the institutions using it.
PHP's emergency patches provide a route back to normal operations for supported installations. They do not resolve the position of organisations whose essential services still run on abandoned branches.
For those institutions, the immediate security decision is inseparable from a longer-standing investment decision: whether to rebuild ageing applications, assume responsibility for maintaining unsupported software, or accept that services once considered permanently available may have to remain disconnected from the public internet.
Sources: Tenable, DEV, The International News, BBC, Rappler, Lusa
