Confession: when the PHP advisory landed last Wednesday, my first instinct was to schedule the update for the weekend. Critical bug, sure, but I'd read "high attack complexity" in the score and told myself I had time. Then I lined up the dates for the six days that followed, and the weekend plan looked a lot worse.
Short version for the impatient: waiting on CVE-2026-109618 and CVE-2026-109619 costs you more each day than the score suggests, because the attack side moved faster than the advisory implied. Below is the timeline as I can source it, what a late patch actually risks, and what I'd check if you already waited.
I'm a developer who runs PHP for clients, not an incident responder. Where I'm guessing, I'll say so.
The timeline, with sources
Here's what I can pin to a source, in order.
On October 20, a post about two critical PHP bugs appeared on Hacker News and was removed, but screenshots spread.…