Is your site exposed to PHP2Shell?
PHP2Shell is a pair of critical, actively-exploited remote code execution flaws in the PHP core — CVE-2026-109618 and CVE-2026-109619 (CVSS 9.2). They affect virtually every web-serving PHP install from 5.4 through 8.5 and let an unauthenticated attacker run code and drop a web shell. Run the free check below to understand your exposure and exactly what to do next.
Assess your exposure
Answer five quick questions about the server that runs your website. Nothing is sent anywhere — the assessment runs entirely in your browser.
Answer the questions and your personalised risk verdict and next steps will appear here.
A leaked PHP flaw that's already being exploited
Details of PHP2Shell leaked on 20 October 2026, ahead of coordinated disclosure, and official patches followed on 21 October. Honeypot operators observed exploitation attempts as early as 17 October — so if you run PHP, assume opportunistic scanning is already reaching your servers.
CVE-2026-109618 — memory corruption
If memory runs out while a request's internal data is only partly initialised, later cleanup treats that data as valid — opening the door to corruption and code execution.
CVE-2026-109619 — use-after-free
Leftover request state outlives the memory it points to, so a later request on the same worker can touch freed memory. Memory disclosure is a confirmed impact, which can leak credentials and API keys.
Find your branch
PHP states that updating is the only complete fix. Mitigations reduce risk but do not make an install safe.
| PHP branch | Status | What to do |
|---|---|---|
| 8.5.x | Affected before 8.5.12 | Update to 8.5.12 |
| 8.4.x | Affected before 8.4.27 | Update to 8.4.27 |
| 8.3.x | Affected before 8.3.36 | Update to 8.3.36 |
| 8.2.x | Affected before 8.2.35 | Update to 8.2.35 |
| 8.0.x / 8.1.x | Affected — no upstream release | Apply the PHP security team's source backport or your vendor/LTS backport; upgrade to a supported branch |
| 7.0 – 7.4 | Affected — no upstream release | Upgrade to a supported branch, or get a backport from your distribution / LTS vendor |
| 5.4 – 5.6 | Affected — end of life | No fix from PHP. Upgrade to a supported release as a priority |
Check the version that actually serves requests
Don't trust php -v alone — it reports the command-line binary, which can differ from the PHP-FPM pool or Apache module that serves your site. Vendors also backport fixes without changing the version number, so check the changelog for the CVE IDs.
Interim mitigations & warning signs
These buy time — they are not a substitute for updating. Restart every PHP worker after any configuration change, and apply settings where applications can't override them (not via ini_set() or .user.ini).
Stopgap mitigations
- Set
session.upload_progress.enabled=0inphp.inior the FPM pool - On PHP 8.5, also set
fatal_error_backtraces=0 - Enforce a finite, non-overridable
memory_limitand a container/cgroup memory limit - Limit
post_max_size; if you don't accept uploads, blockmultipart/form-dataPOSTs at the proxy - Add WAF rules as a temporary shield; isolate or take internet-facing apps offline if you run 8.1 or earlier (per CISA / CERT-EU)
Indicators of compromise
- Unusual multipart requests followed by memory-limit errors or repeated HTTP 500s
- Oversized or malformed
PHPSESSIDcookies - Web shells, unexpected or modified PHP files, or new admin users
- Unexpected child processes spawned by PHP, or unusual outbound connections
- Review logs from 17 October onward; if compromise is suspected, rotate database credentials and API keys
Let Aurora do it for you.
Our engineers will inventory every PHP runtime you operate, patch and rebuild them to a fixed release, apply hardening and WAF rules, review your logs for exploitation since 17 October, and verify you're clean — with zero downtime where possible.
This self-assessment is a guidance tool to help you prioritise remediation; it does not scan your systems and is not a guarantee of security or a substitute for a full audit. Vulnerability details reflect the official PHP security releases of 21 October 2026 and public advisories. Always confirm affected and fixed versions against the official PHP release notes and your distribution's advisories before acting.