What is confirmed
CERT-FR published its alert on 21 October and updated it on 26 and 27 October concerning CVE-2026-109618 and CVE-2026-109619.
Fixed branches include PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12; the 5.x, 7.x, 8.0 and 8.1 branches are end of life.
CERT-FR reports exploitation attempts against specific deployments and references a third vulnerability, CVE-2026-115560, disclosed on 23 October under less common conditions.
What it means
Running PHP on a server does not automatically mean it is exploitable; execution mode and application configuration matter.
Temporary mitigations were documented, but CERT-FR says updating is the only complete protection against the affected flaws.
Identify deployed PHP runtimes
Inspect each PHP-FPM pool, container, extension and product bundling PHP—not only the host's CLI version. Third-party products need their own advisories.
Patching and intrusion review
After patching, review logs and suspicious activity indicators on components exposed before the update.
What to do
Inventory exposed versions and update to a fixed release for each supported branch.
Isolate systems that cannot be patched promptly and use vendor workarounds only as temporary controls.
Monitor anomalous errors and requests and investigate possible compromise after patching.
Use the related SecurCheck tool, then confirm important decisions with an official source.