Updated 21 October 2026, before the scheduled security release. The PHP security team has announced two critical vulnerabilities, each rated 9.2 under CVSS v4.0, with a release scheduled for 14:00 UTC (15:00 BST) today. The official announcement has not yet published the affected and fixed PHP versions or technical root causes. Treat version-specific claims circulating before the release as unconfirmed until checked against PHP's own release notes.
1. What is known — and what remains uncertain
- Confirmed by the PHP team: an upcoming security release covers two critical vulnerabilities, both scored 9.2 on CVSS v4.0.
- Scheduled publication: 21 October 2026 at 14:00 UTC. The team may release earlier if circumstances change.
- At the time of this guide, the PHP team has not confirmed affected or fixed version numbers in its announcement.
- CERT-EU warns that reported impact could include unauthenticated remote code execution, but says technical details are not yet public. Avoid treating circulating proof-of-concept claims as verified facts.
2. Find out where PHP is running
List your PHP-powered applications, including WordPress, Drupal, Joomla, Magento, custom sites, admin panels, background workers and staging systems. Include hosting providers, container images and managed platforms. Record the owner of each deployment, whether it is reachable from the public internet, its PHP version and how updates are delivered.
php -v
# If using Docker, also list the running images:
docker ps --format 'table {{.Names}}\t{{.Image}}'For WordPress, use Tools → Site Health → Info → Server to locate the server PHP version where available. If you use managed hosting, ask your provider which runtime is deployed and who is responsible for applying the PHP security update.
3. Prepare the update before the fixed builds arrive
- Prioritise internet-facing production systems and any administrative interfaces exposed to the internet.
- Confirm you have a recent, restorable backup of files and databases, plus a tested rollback path.
- Check your PHP support lifecycle and the update process for your operating system, managed host or container base image.
- Test key user journeys in staging: sign-in, payments, forms, scheduled jobs and API calls.
- Assign an owner to watch the official PHP release notes and your operating system or hosting vendor's advisories.
4. Patch and validate when official fixes are available
- Read the official release notes to identify which versions are affected and which builds contain the fixes. Account for backported security patches supplied by your Linux distribution or hosting vendor.
- Update the relevant PHP runtime or container base image through the vendor-supported path. Rebuild and redeploy images where applicable; merely changing a Dockerfile does not update running containers.
- Restart or replace the affected PHP workers, then verify the version and patch provenance in the environment actually serving requests.
- Run a smoke test of critical functionality and inspect server and application logs for new errors.
- Confirm all production replicas, staging instances and scheduled workers are accounted for, then document the completion time.
5. What if you cannot patch immediately?
CERT-EU recommends considering isolation of internet-facing applications from public networks where immediate patching is not feasible. Depending on business needs, temporary access restrictions, maintenance mode, network segmentation or taking a vulnerable service offline may be warranted. A web application firewall can be a temporary additional control, not a substitute for applying the actual fix; effectiveness depends on the vulnerability and available detection rules.
6. How to check your website afterwards
- Verify the patched PHP build or vendor backport on every active deployment.
- Check that the homepage, login, forms, APIs and scheduled jobs still work.
- Review error rates, uptime, access logs and unexpected changes after redeployment.
- Keep monitoring the public website, but distinguish outside-in checks from server-level patch verification.
An external website monitor such as Zenith can help track visible signals such as availability and web security configuration. It cannot, on its own, establish that an internal PHP installation received a specific security patch. Treat runtime inventory and patch confirmation as separate required steps.
Official sources and further reading
- PHP security-team announcement: https://www.php.net/archive/2026.php#2026-10-20-1
- PHP Foundation announcement: https://discourse.thephp.foundation/t/announce-upcoming-critical-php-security-release/6251
- CERT-EU advisory 2026-018: https://cert.europa.eu/publications/security-advisories/2026-018/
- Australian Cyber Security Centre alert: https://www.cyber.gov.au/alert/critical-vulnerabilities-in-php
Glossary
- PHP runtime
- The version and configuration of PHP that actually executes a website's server-side code.
- CVSS
- Common Vulnerability Scoring System, a framework for rating vulnerability severity. The announced score uses version 4.0.
- PHP-FPM
- A common PHP process manager that serves PHP requests separately from the command-line PHP installation.
- Backport
- A vendor's application of a security fix to an older supported software package without necessarily changing its upstream version number.