
The October PHP security fixes needed urgent attention. Applying the updates was one part of the job; checking the pages afterwards mattered too.
On 21 October 2026, the PHP project released fixes for two critical vulnerabilities that could allow unauthenticated remote code execution. The identifiers are CVE-2026-109618 and CVE-2026-109619.[1][2][3]
We treated the updates as urgent. We applied PHP security updates on 22 October and checked the rendered pages afterwards, rather than stopping at an update confirmation.
For a website owner, that second part deserves some attention. You want the security fix applied, but you also need to know that people can still use your site.
The PHP project’s advisory covered installations serving web requests, not just one CMS or one type of website. The October fixes were released in PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. PHP also directed people using distribution packages to check their vendor’s updates.[1]
Those are the releases associated with that advisory. They are not a promise that installing one version number deals with every future issue. PHP published additional session-related configuration guidance on 23 October, so anyone reviewing their position now should read the current vendor advice too.[1]
There is no need for a business owner to become a PHP security specialist. There does need to be someone responsible for reading those notices and acting on them.
Our checks compared rendered pages before and after the work. We checked that the expected page content appeared, rather than accepting a successful HTTP response as enough evidence on its own.
A useful maintenance question is, “What did you check after the update?” That should produce a more useful answer than “the command finished”.
For your own site, agree which pages and actions need checking. A brochure site might need its main pages and enquiry route checked. A shop needs a suitable test of the buying journey. Those are checks to agree for the particular website, not a claim that every maintenance visit includes the same list.
Ask whether the relevant PHP fixes have been applied, which vendor supplies the packages, and what was checked afterwards. If older software needs a separate upgrade plan, get that plan written down rather than leaving it as an assumption.
Keep the response specific. A completed update, a checked page and an unresolved compatibility question are different things and should be reported separately.
If you are unsure who looks after the PHP behind your website, talk to us. That is a sensible place to start before the next security notice arrives.