TL;DR: Nearly every modern PHP release can stay exposed to PHP2Shell after application patching, according to Pentera. Runtime verification and worker restarts now matter because the interpreter, not the app, can remain the vulnerable path.
Editorial analysis by NHI Mgmt Group, based on content published by Pentera: “PHP2Shell: the expiry date on “too hard to exploit””.
By the numbers:
- PHP2Shell includes two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, both scored CVSS v4.0 9.2.
Key questions
Q: Why does a runtime patch not always mean the service is safe?
A: Because the running worker may still be using the old binary after the package update.
Q: What signs suggest interpreter-level exposure is still present after patching?
A: If the version on disk differs from the version actively serving traffic, the exposure remains.
Q: What breaks when teams rely on CMS patching but leave the PHP runtime exposed?
A: The assumption that application-layer hardening is enough breaks down.
Practitioner guidance
- Patch the interpreter to a fixed release Move PHP to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or use your distribution’s backport if you are on an older supported branch.
- Restart every runtime worker after upgrading Restart Apache, PHP-FPM and any long-running workers, then confirm the version actually executing requests rather than the package version stored on disk.
- Treat older unsupported PHP branches as exposed Assume 8.1 and older remain exposed unless you have a verified backport, and check bundled runtimes inside containers, appliances and control panels.
Bottom line: PHP2Shell matters because the vulnerable layer is the interpreter itself, so patched applications can still remain exposed if the runtime is old or unrestarted.
Glossary terms: Interpreter-level vulnerability, Live worker verification, Exposure Debt, Request parsing attack surface
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Interpreter vulnerabilities should be treated as identity-adjacent control failures, not application bugs. When the runtime under a web application is exploitable before the application starts, every downstream identity control becomes conditional on a compromised execution layer. That shifts the governance question from whether the app is patched to whether the trust boundary around the worker is real. Practitioners should treat runtime integrity as part of access governance, not a separate infrastructure concern.
A question worth separating out:
A: Contain the vulnerable path first, then reduce the chance that the exploit can trigger. For PHP2Shell, that means disabling the specific feature paths called out in the advisory, tightening restart and version checks, and prioritising the runtime upgrade over routine maintenance work. The objective is to remove the exploitable condition, not to assume logging or suppression will contain it.
👉 Read our full editorial: PHP2Shell shows how interpreter flaws bypass application-level defenses