On October 21, the PHP team released fixes for two critical flaws (CVE-2026-109618 and CVE-2026-109619) that could allow attackers to run code without logging in. Node.js received patches too, addressing code execution and bypasses of HTTPS certificate checks.
On October 21, we released PanelAlpha Control Panel and Engine updates with the PHP fixes available at the time. More patches followed, and the Engine updates released on October 22 cover them too. Both Engine v1.0.23.2 and v2.1.2.2 include updated PHP in phpMyAdmin and Node.js in Lighthouse. Engine 1.x also has patched PHP for LiteSpeed sites and the extra session protection introduced in Engine 2.x on October 21.
With both releases now out, we’ve completed this round of PHP and Node.js security updates. All relevant fixes are now in place across Engine’s supported components. PHP 7.4, 8.0 and 8.1 are also covered by backported security fixes in our updated Engine images, although we still recommend moving to a supported PHP version.
If you read our October 21 security update, this is the next step: what else we have patched, and what you still need to check on your servers.
What we have updated in Engine
The updates cover slightly different components in each Engine generation, but the priority remains the same: making sure the services included with Engine use patched PHP and Node.js builds.
PanelAlpha Engine 1.x → update to v1.0.23.2
We have updated PHP 8.2, 8.3 and 8.4 for customer sites running on LiteSpeed. The PHP version inside phpMyAdmin has also been updated, along with the Node.js runtime used by Lighthouse for website performance checks.
We’ve also strengthened PHP session handling and included backported fixes for PHP 7.4, 8.0 and 8.1, including LiteSpeed sites. These PHP versions are no longer supported by the PHP team so upgrading to PHP 8.2 or newer is still recommended.
PanelAlpha Engine 2.x (open source) → update to v2.1.2.2
Engine 2.x now includes updated PHP in phpMyAdmin and Node.js in Lighthouse. We’ve also prepared patched PHP 8.2, 8.3 and 8.4 images for LiteSpeed, ready for when LiteSpeed support returns to Engine 2.x. For now, websites on Engine 2.x run through nginx. On new installations, Engine also downloads a ready-made web server image instead of building it directly on the server. Sites running PHP 7.4, 8.0 or 8.1 through PHP-FPM also receive backported security fixes in the updated Engine images.
For Node.js applications built directly by Engine, the updated runtime will be picked up on the next deployment. If your project uses its own Dockerfile or docker-compose configuration, you’ll need to update the Node.js image yourself and redeploy the application. Engine won’t do that automatically.
PHP 7.4, 8.0 and 8.1: patched, but still unsupported
Although PHP 7.4, 8.0 and 8.1 no longer receive official updates from the PHP team, the images included in our latest Engine releases already contain backported fixes for both critical vulnerabilities (CVE-2026-109618 and CVE-2026-109619). These cover PHP-FPM sites on Engine 1.x and 2.x, as well as LiteSpeed sites on Engine 1.x. We still strongly recommend upgrading to PHP 8.2 or newer for ongoing security support. Updating Engine does not automatically change the PHP version selected for your existing sites.
What you should do now
- Update your Engine installation. Even if you applied the October 21 fixes, update Engine to either v1.0.23.2 or v2.1.2.2 depending on your setup. You’ll find the instructions in our Engine 1.x update guide or Engine 2.x update guide.
Using Control Panel with Engine? Stick with your current Engine generation for now and update it to v1.0.23.2. We’re already working on the dedicated Control Panel update that will let you move to Engine 2.x once it’s ready.
- Check the PHP version of each site. Our latest Engine updates already include backported fixes for PHP 7.4, 8.0 and 8.1, but these versions are no longer maintained by the PHP team. We still recommend moving to PHP 8.2 or newer. Remember to check scheduled tasks as well as your websites.
- Check your Node.js applications on Engine 2.x. If you’re still using Node.js 18 or 20, move to a patched version of Node.js 22 or 24 first. Applications built by Engine will pick up the updated runtime when redeployed. For projects using a custom Dockerfile or docker-compose configuration, update the Node.js image manually, then rebuild and redeploy.
- Make sure everything is working. Check a few hosted sites, phpMyAdmin and performance tests, then review the logs for anything unusual.
What about Client and Admin Areas?
The Node.js vulnerabilities announced on October 21 do not affect the PanelAlpha Client Area or Admin Area, because neither uses Node.js at runtime. These additional Node.js updates concern the Engine components mentioned above and Node.js applications deployed by users.
Keeping your Engine protected
Over the past two days, we have worked through the places where Engine uses PHP and Node.js, including the ones you do not normally see when managing a website. With this follow-up, the Engine builds we maintain now include all relevant fixes for the vulnerabilities disclosed on October 21.
But don’t let your guard down just yet. With the relevant PHP fixes now included across our Engine images, upgrading from unsupported PHP versions remains an important long-term step rather than a requirement for these particular patches. For Node.js applications on Engine 2.x, make sure you’re using a supported, patched runtime. Projects with custom Dockerfile or docker-compose configurations still require a manual Node.js image update and redeployment.
If you installed the October 21 Engine update, please make sure you’ve also updated to v1.0.23.2 or v2.1.2.2.
Further reading
- PanelAlpha security update (October 21, 2026)
- Official PHP news archive (2026)
- Node.js security releases (October 2026)
Not sure what this means to your installation?
If you have questions about the updates, your PHP versions or any of the steps above, come talk to us on Discord. We are happy to help you check what needs attention.
Join us on Discord →
Comments