🔍 Read the full analysis: The Dutch Government Website Outage And The PHP Flaws Exposed By PHP2Shell on ThorstenMeyerAI.com
Get hardware and tech essentials delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
PHP released emergency fixes on October 21 for two critical vulnerabilities that can enable unauthenticated remote code execution. The Dutch government took several services, including Overheid.nl, MijnOverheid.nl and DigiD, offline as a precaution; it said there were no signs those services had been actively exploited at the time of its statement.
The Dutch government took several public websites offline, including Overheid.nl, MijnOverheid.nl and DigiD, on October 21 as a precaution after PHP disclosed two critical vulnerabilities that can allow unauthenticated remote code execution. The government said it had no signs of active exploitation at the time of its announcement; the shutdown was preventive and does not establish that those services were compromised.
PHP’s security team released emergency updates for vulnerabilities CVE-2026-109618 and CVE-2026-109619, collectively referred to as PHP2Shell. Both advisories carry a CVSS v4.0 score of 9.2, rated Critical. PHP says web-facing installations can be at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed.
The flaws involve PHP’s handling of memory and internal request state when processing is interrupted. The first can cause cleanup to use request data that was not fully initialized after an out-of-memory failure. The second can leave references to memory after it has been freed. Those conditions can cause memory corruption or use-after-free errors and, under affected conditions, remote code execution. PHP’s advisory reports demonstrated exploitation on Apache with mod_php. It says execution occurs as the web worker account, which does not by itself mean administrator or root access.
Fixed releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP also provided minimal source backports for versions 7.4, 8.0 and 8.1. Those versions are outside normal upstream support, so organizations using vendor or extended-support packages need to check for a fixed package from their provider. A version number alone may not reveal whether a vendor backport is included.
Why Runtime Patching Matters
PHP2Shell affects the PHP runtime beneath websites, rather than a particular content-management system or plugin. Updating WordPress, Drupal or Joomla code alone does not fix an affected PHP installation. Researchers at Wiz demonstrated unauthenticated code execution against deployments of those systems, illustrating how a flaw in the shared runtime can affect different applications.
The practical question for businesses and publishers is whether the PHP software serving each site has been patched. Managed-hosting customers may not control that runtime directly and should seek confirmation from their provider. Operators that manage their own servers need to identify which PHP branch and request-handling configuration are in use, install the appropriate fixed package, and verify that patched software is actually serving traffic.
The incident also affects public access to government services: precautionary shutdowns can disrupt users even when no compromise has been confirmed. The Dutch National Cyber Security Centre urged organizations to update and said systems that remain unpatched should stay offline as a precaution. Separately, Cloudflare reported seeing attack traffic and attempts to alter payloads to bypass protections. Those observations show attempted exploitation, but do not prove that the named Dutch services were attacked successfully.
Products Worth Considering

Apple MacBook Pro 14.2-inch with M5 Pro, 15-Core CPU, 16-Core GPU, 24GB Memory, 2TB SSD, Wi-Fi 7, Space Black

Apple MacBook Air 15-inch Laptop with M5 Chip, 16GB Memory, 512GB SSD, Midnight

Apple MacBook Air 13-inch with M5 Chip, 16GB Memory, 512GB SSD, Midnight
As an affiliate, we earn on qualifying purchases.
How the Dutch Shutdown Unfolded
The Dutch government’s October 21 announcement said several services were taken offline before patches were available, as a precaution against the newly disclosed flaws. It reported no signs of active exploitation at the time. The announcement also said that many government websites, including Rijksoverheid.nl, did not use PHP and were not affected by these particular vulnerabilities.
The National Cyber Security Centre later confirmed patches were available and urged organizations to apply them. Its guidance said systems that had not been updated should remain offline as a precaution. That guidance reflects the risk posed by an exposed, unpatched runtime; it is not evidence that every vulnerable system was attacked.
The vulnerability reports describe differences between server configurations. PHP’s advisories document demonstrated exploitation on Apache with mod_php. Research from Calif says PHP-FPM handles some startup failures differently, but also describes application-dependent paths that may be exploitable in PHP-FPM environments. That distinction does not establish PHP-FPM as immune; operators need to assess the particular runtime, configuration and application.
The disclosure also involved AI-assisted security research. OpenAI said Calif identified a critical flaw using GPT-5.6 Sol through its Patch the Planet initiative, while Wiz independently discovered and reported both vulnerabilities. PHP maintainers issued the fixes, with researchers and infrastructure providers contributing. Calif said its discovery used generally available models and depended on researcher guidance informed by PHP’s vulnerability history. These accounts describe research methods, not a separate security issue affecting PHP users.
“The websites were taken offline as a precaution; the government said it had no signs of active exploitation at the time.”
— Dutch government announcement
What Is Known About Exposure
The available announcements do not say whether the Dutch websites were targeted, whether attackers gained access to any other vulnerable systems, or when the affected public services would return. The government reported no signs of active exploitation at the time of its statement, but that is a time-specific assessment, not proof that no attempt occurred later.
Cloudflare’s observations of attack traffic do not identify the Dutch services as successfully compromised. The source material also does not provide a complete count of vulnerable PHP installations or affected organizations. Exposure depends on the PHP version, server configuration and application; the presence of a named CMS does not by itself establish vulnerability, and a vendor backport may not be obvious from a version string.
Patching and Service Restoration
Operators should install the fixed PHP package for their branch, or obtain a patched package from their distribution, hosting provider or extended-support vendor. They should then verify that the updated runtime is the one handling web requests. Where patching is not yet possible, the Dutch NCSC’s guidance is to keep the affected system offline as a precaution.
For customers on managed hosting, the next step is to ask providers whether the PHP runtime serving each site has been updated. For the Dutch services, the source material does not give a restoration schedule. Their availability and any further government findings will depend on the authorities’ assessment and remediation work.
Key Questions
Were the Dutch government websites confirmed to be hacked?
No. The government said the websites were taken offline as a precaution and that it had no signs of active exploitation at the time of its announcement. That statement does not confirm a compromise.
Which PHP versions include the fixes?
The listed fixed releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP also supplied minimal source backports for 7.4, 8.0 and 8.1; users should confirm that their vendor has packaged and applied a fix.
Will updating WordPress or a plugin fix PHP2Shell?
No. The flaws affect the PHP runtime, so updating website code or plugins alone does not patch them. The runtime serving the site must be updated.
Are PHP-FPM websites safe from these vulnerabilities?
The source material does not establish that PHP-FPM is immune. Researchers describe some differences in how it handles startup failures, alongside application-dependent exploitation paths. Risk depends on the particular setup, and operators should install the relevant fix.
Source: ThorstenMeyerAI.com
