Critical PHP RCE Flaws Prompt Patching as Scanner Fixes Expose False-Safe Results
Vulnerability Disclosure · 13 sources · Updated 2h ago · First seen Nov 19, 2026

Two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, can enable unauthenticated remote code execution in web-serving installations, according to Red Sift. Both carry reported CVSS v4.0 scores of 9.2 and involve out-of-memory corruption and stale per-request state. Apache mod_php is identified as the highest-risk deployment because a demonstrated exploit runs during request parsing, before application code executes. The PHP security team reportedly released fixes in PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. Organizations should inventory standalone and embedded PHP installations, apply fixed releases or vendor backports, restart all workers, and investigate potentially compromised systems; configuration mitigations do not replace patching.
Subsequent php2shell testing reported vulnerable behavior across tested end-of-life PHP 5.6–8.1 releases and uncovered false SAFE verdicts, incompatible warning matchers, and a broken upstream Nuclei template. Repository updates corrected detection and defensive-rule logic and distinguished inconclusive results from patched systems. Remote checks on PHP 7.4 and earlier depend on exposed startup warnings, so missing signatures do not establish safety. The repository also added prerequisite checks for CVE-2026-115560, a session serializer mismatch it says remains unfixed in the releases above. Exploitation requires an application-level runtime handler switch that the checker cannot confirm; the maintainers recommend disabling session upload progress to close the described poisoning path. The supplied references do not document a victim incident or observed exploitation campaign.


