The PHP project has shipped emergency fixes for two critical flaws that can let an attacker take over a web server with a single request. The US National Security Agency told organisations that can’t patch right away to take their systems offline.
By HahuPrime News Desk | October 21, 2026

WASHINGTON — The National Security Agency issued an unusually blunt warning on Wednesday about PHP, the programming language that runs most of the web. “Effective Immediately, all organizations using PHP for their systems are advised to be prepared for an update addressing two critical vulnerabilities,” the agency said in a statement on nsa.gov.
“These vulnerabilities often provide a direct path to the server’s file system or database,” the NSA said. “If an immediate update is not feasible, it is recommended that organizations take the system offline until it can be fully mitigated.” It said more detailed guidance would follow.
A few hours later, the PHP project released the fixes.
What the flaws are
PHP’s security advisory lists two bugs, each rated 9.2 out of 10 on the CVSS v4.0 scale. Both can allow unauthenticated remote code execution, meaning an attacker can run their own commands on the server without logging in.
- CVE-2026-109618 (GHSA-w8hw-w9fx-j79w): when a request runs out of memory, PHP can be interrupted while internal request data is only partly set up. The cleanup step may then treat that broken data as valid.
- CVE-2026-109619 (GHSA-6wmf-4rv5-p3rp): internal state from one request can survive after its memory has been freed. A later request handled by the same worker may use that stale state.
According to the PHP team, every PHP installation that serves web requests is at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. It considers mod_php the most dangerous setup. In a demonstrated exploit, one unauthenticated request triggered the attack before any application code ran.
Which versions to install
The fixed releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. EU cybersecurity body CERT-EU said they went live at 13:30 UTC on Wednesday. PHP had warned on Tuesday that the release was coming.
PHP 8.1 and older no longer get official updates. Because of the severity, the PHP security team published minimal source backports for PHP 7.4, 8.0 and 8.1, and some Linux distributions and long-term support vendors offer their own patched packages. PHP 8.2 reaches end of life on December 31, 2026.
The PHP team stressed that only an update fully fixes the problem. For those who can’t update straight away, it listed stopgaps that reduce exposure, such as turning off session.upload_progress.enabled and lowering post_max_size. It warned that these steps “do not make an installation safe.”
Sites going dark
CERT-EU said technical details are now being discussed publicly and early proof-of-concept exploits are circulating. That makes it more likely attackers are already using the flaws. Government agencies in the Netherlands and Finland took sites offline as a precaution, CNBC reported, and the Dutch cybersecurity agency took its own site down too. Britain’s NCSC told UK organisations to find every PHP system they run, starting with internet-facing ones.
Cloudflare’s chief technology officer, Dane Knecht, said the company was seeing “early attacks emerging” and was updating its firewall rules, but called that “a STOPGAP only.”
Why WordPress owners must act themselves
Every WordPress site runs on PHP. According to W3Techs figures cited by CNBC, PHP powers about three-quarters of websites whose server language can be identified. The security firm Wordfence warned that WordPress’s automatic updates will not apply this fix, because PHP sits underneath WordPress on the server. Site owners need to find out who is responsible for updating PHP on their host.
That matters a great deal in Africa, where news sites, schools, NGOs, small businesses and many government portals run on WordPress or other PHP software on cheap shared hosting. On those plans the customer often can’t update PHP at all, so the hosting company has to do it. Owners should:
- Check the PHP version in their hosting control panel (cPanel, Plesk or similar), or under Tools > Site Health > Info > Server in WordPress.
- Ask their host in writing whether PHP has been updated to one of the fixed versions, and when.
- If they run their own server, install the update from their distribution and restart every PHP worker.
- If a site can’t be patched soon, consider taking it offline for now, as the NSA advises, and check it for signs of compromise before bringing it back.
The flaws are another sign of how fast attacks now spread. We recently reported on a hacker who used AI agents to break into more than 100 company websites. Governments are also tightening control of the software on their own systems, as with the US order removing DeepSeek from federal systems. For Africa’s push to build digital infrastructure, covered in our report on the World Bank’s AI computing plan, basic patching remains the first line of defence.
Sources: NSA, PHP project security advisory (php.net), CERT-EU, UK NCSC, CNBC.