Key points
- PHP published security releases on 21 October 2026 for CVE-2026-109618 and CVE-2026-109619, two critical vulnerabilities that can allow unauthenticated remote code execution.
- The PHP project identified PHP installations serving web requests as potentially at risk. In its demonstrated exploit, it described the highest risk for Apache with mod_php, where PHP runs as part of the Apache web server.
- CISA’s Known Exploited Vulnerabilities catalogue lists both CVEs. That is a global threat signal, not evidence that a particular organisation was breached.
- Confirm the actual runtime, deployment mode, version and vendor patch status. A version string alone does not establish whether a system is exposed or compromised.
Information checked against the linked primary sources on 10 November 2026. Recheck the PHP project and CISA before acting; vulnerability guidance and supported package status can change.
What does “PHP2Shell” refer to?
PHP2Shell is the name used in reporting about two PHP runtime vulnerabilities disclosed by the PHP project on 21 October 2026: CVE-2026-109618 and CVE-2026-109619. The PHP security advisory describes both as critical remote code execution vulnerabilities. In practical terms, successful exploitation could allow an attacker to execute code on a vulnerable server under the privileges available to the PHP process. The consequences depend on the server’s permissions, isolation, connected services and the data or systems it can reach. PHP project security advisory: critical remote code execution vulnerabilities, 21 October 2026
The PHP project describes different underlying failure conditions: one involves memory handling during an out-of-memory condition; the other involves stale request state. The important operational point for most application owners is to identify the runtime that actually serves requests and confirm that the vendor-provided security fix is present. A website’s framework or CMS version does not, by itself, tell you which PHP runtime package is running.
What do the global facts tell us?
The PHP project announced fixed releases for PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on 21 October. Older releases should be checked with the Linux distribution or long-term-support vendor. A vendor may apply the security fix to an older-looking package without changing it to the PHP project’s version number; compare with the package provider’s advisory instead of relying only on the version number. PHP project security advisory: critical remote code execution vulnerabilities, 21 October 2026
CISA’s Known Exploited Vulnerabilities catalogue includes CVE-2026-109618 and CVE-2026-109619. The catalogue records vulnerabilities for which exploitation evidence is known to CISA. It signals that organisations should treat the advisories seriously, but it does not say which individual websites were targeted or compromised. CISA notice adding CVE-2026-109618 and CVE-2026-109619 to the KEV Catalog, 26 October 2026
A separate informational note published on 23 October describes an unusual configuration and application-code combination involving session upload progress that could create another RCE vector. The PHP project said a full advisory for CVE-2026-115560 would follow with the next release; that full advisory was not present in the PHP 2026 archive when checked on 10 November. This remains separate from the two PHP2Shell CVEs above. PHP security advisory: CVE-2026-115560 and session upload progress
PHP 8.2 is scheduled to reach end of security support on 31 December 2026. The PHP project’s release archive says it will receive no further security fixes after that date. Teams still using that branch need to plan both the immediate security update and a supported-version path. PHP 2026 news archive: supported branches and security releases
Who may be affected?
The PHP project’s advisory says PHP installations serving web requests may be at risk. It names PHP-FPM (a separate PHP process manager), Apache with mod_php (PHP running as part of the Apache web server), php-cgi (PHP called as a separate program), FrankenPHP and LiteSpeed. The demonstrated exploit presented the highest risk for mod_php. This is a reason to check the deployed setup, not to assume every PHP application has the same exposure.
PHP may be maintained by a hosting provider, managed service provider, software vendor or internal engineering team. If you do not administer the runtime, ask the responsible provider to identify the PHP package and deployment mode in production, confirm the applicable security fix, and provide evidence of when it was applied.
How should an organisation understand its risk?
Do not use a three-colour label or vulnerability headline as a substitute for checking the environment. A useful initial triage separates three questions:
1. Is the affected runtime present?
Confirm which PHP setup handles live requests, the exact package and vendor version, and whether the provider applied the security fix to an older package version. Check all relevant hosts, containers and environments; a test environment may not match production.
2. Is the vulnerable condition present and reachable?
Use the official advisory and the package maintainer’s guidance to assess whether the affected condition applies. Consider how requests reach PHP, what parts of the application are exposed, and what isolation and permissions constrain the PHP process. A remote scan can provide clues, but may not reliably identify a vendor-applied fix or prove that vulnerable code is absent.
3. Is there evidence of compromise?
A vulnerable or unpatched system is not automatically a compromised system. Conversely, installing an update does not establish that no attacker accessed the system earlier. If there are unexplained processes, files, accounts, outbound connections or other indicators, treat that as a separate incident question. Preserve relevant evidence and use the organisation’s incident process and qualified response provider.
What should you do next?
- Ask the PHP administrator, host or software vendor to confirm the production runtime, deployment mode and package status against the official advisory.
- Apply the relevant vendor security update through the organisation’s change process, then confirm the running workers and instances use the updated package.
- Where an update cannot be applied promptly, follow the exact vendor advisory for temporary exposure-reduction measures. The PHP project says its listed workarounds do not make an installation safe; do not treat them as a replacement for updating.
- If compromise is suspected and you have no incident team, contact the organisation that manages your hosting or IT systems and ask for help from a qualified incident-response provider. Preserve relevant evidence; a routine vulnerability check is not a breach investigation.
- Record what was checked, by whom, when, which assets were in scope and what remains uncertain.
Avoid making configuration changes copied from a general article without an administrator who understands the application and vendor guidance. Some mitigations affect application behaviour or availability.
What a scoped security check can establish
A security assessment can help verify the runtime and relevant conditions, validate findings, review code and dependencies within agreed scope, and prioritise remediation. Fixes and a retest should have clear owners and boundaries. The assessment cannot guarantee that an application is free of vulnerabilities or prove that no compromise occurred.
Bravewall’s proposed PHP Application Security Check is intended for organisations of any size that operate PHP applications. The current package is a scoped assessment with validated reporting and one retest; agreed application fixes are handled separately by the application development team. Suspected compromise investigation is separate. Until Bravewall confirms an incident service, contact your hosting or IT provider to find a qualified response provider.
Sources and update note
The release versions and affected runtime notes above come from the PHP project’s 21 October advisory. The exploitation-status statement refers to CISA’s catalogue. The PHP 8.2 support date comes from the PHP project release archive. This article does not infer customer-specific impact from those sources.

