On 21 October 2026, the PHP project released emergency fixes for two critical flaws, nicknamed "PHP2Shell". They can let an attacker run their own commands on a web server without logging in. Within days they were being exploited, and the UK's National Cyber Security Centre (NCSC) urged organisations to act immediately. Two days later, PHP warned of a third flaw that is not yet fixed.
You may never have heard of PHP, but there is a good chance it is behind your website. Here is what happened, in plain English, and what to do about it this week.
What happened
- CVE-2026-109618 and CVE-2026-109619 are both rated 9.2 out of 10 for severity. They affect any PHP installation that serves web pages, including the most common set-ups (Apache with mod_php, PHP-FPM, php-cgi, LiteSpeed and FrankenPHP).
- They are fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. PHP 8.1 and earlier no longer receive fixes from the PHP project.
- Attacks were seen from 21 October, and the US cyber agency CISA added both flaws to its list of known exploited vulnerabilities on 26 October.
- A third flaw, CVE-2026-115560, was announced on 23 October and is not covered by the 21 October updates. It needs an unusual combination of settings to exploit, and PHP's interim advice is to switch off the "session upload progress" feature until a fix is released.
Why it matters even if you don't "use PHP"
PHP runs a large share of the world's websites, including WordPress, many online shops, booking systems, intranets and hosting control panels. It is also built into some firewalls, routers and other appliances, where it is not obvious. The NCSC's advice is that all versions may be affected, so the question is not "are we on an old version?" but "where is PHP running for us at all?"
What to do this week
If someone else runs your website or IT, most of this is a set of questions to ask them. Ask for the answers in writing: that record is useful evidence later.
- Find it. List every website, web application and device you rely on, starting with anything reachable from the internet. Ask your web host, developer or MSP which of them use PHP, including in any third-party products.
- Patch it. Make sure each one is on PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35 or later, internet-facing systems first. On managed hosting, ask your host to confirm the date it was done.
- Retire what can't be patched. Anything on PHP 8.1 or older is unsupported. The NCSC and CISA advise taking systems offline if they can't be updated or mitigated quickly.
- Apply the interim setting. Until the third flaw is fixed, ask for
session.upload_progress.enabledto be set to off, as the PHP security team recommends. - Check for signs of compromise. Because attacks started before many people patched, ask whether anything suspicious has happened, such as unexpected files on the server or the web server starting other programs. If you don't have the skills in house, the NCSC lists assured incident response providers.
- Watch your suppliers. Look for updates from the vendors of any products that include PHP, and keep an eye on the PHP project for the fix to the third flaw.
The compliance angle
This is exactly the kind of event your security framework expects you to handle well, and to be able to show that you did.
- Cyber Essentials requires critical and high-risk security updates to be installed within 14 days of release, and unsupported software to be removed. For these flaws, that means by 4 November 2026 at the latest.
- NCSC CAF outcome B4.d (Vulnerability Management) and ISO/IEC 27001 control 8.8 (Management of technical vulnerabilities) both expect you to know your exposure, fix it promptly and keep a record.
- Cyber insurance policies commonly require software to be kept up to date, and some exclude losses from systems left unpatched or unsupported. A dated record of when you patched is what proves you met that condition.
In practice, the evidence an assessor, customer or insurer will want is simple: an up-to-date asset list showing where PHP runs, a dated entry for each system showing when it was patched (or why it was retired), and confirmation from your suppliers.
How we can help
The CyberSec Compliance platform gives you a Patch & Vulnerability Management Policy tailored to how you actually work, an Asset Register to record where PHP runs, a Vulnerability & Patch Log to record what was fixed and when, and an Action Plan to track anything outstanding with your IT provider or MSP. Each record links to the Cyber Essentials, CAF and ISO 27001 requirements it evidences.
For transparency: our own platform does not use PHP anywhere. We checked our servers and every component after the announcement.
Sources
- NCSC: Critical security issue affecting PHP (21 October 2026, updated 23 October)
- CISA: Critical Vulnerabilities in PHP Require Immediate Patching (updated 26 October 2026)
- Canadian Centre for Cyber Security: AL26-026, Update 2 (27 October 2026)
This article is general guidance, correct at the time of writing. The situation is still developing, so check the PHP project's own security advisories for the latest fixed versions.
