Skip to main content
Exostruction
Back to overview
Alexander Kreitmair5 min read

PHP2Shell and Node.js: what site operators need to check now

Critical PHP flaws and a Node.js security release: which versions are patched and what site operators should check now.

Guide
PHP2Shell and Node.js: what site operators need to check now

On 21 October 2026, the PHP project fixed two critical flaws known as PHP2Shell. The same day, a security release for Node.js followed. Anyone who runs PHP or Node.js, or has it run for them, should now check whether the patched versions are in place. For PHP this matters most, because the flaws sit in the core of the language. A current CMS on top does not help. The comparison is in the section The two flaws at a glance. Status as of 30 October 2026.

The flaw sits below the application: even an up-to-date WordPress does not help if the PHP underneath is old.

PHP2Shell: what happened

On 21 October 2026 the PHP project released versions 8.5.12, 8.4.27, 8.3.36 and 8.2.35. According to the PHP security advisory they fix two critical flaws (CVE-2026-109618 and CVE-2026-109619) that allow attackers to run code on the server without logging in. Both are rated CVSS 4.0 9.2.

What makes this special: the bugs are in the PHP runtime itself. According to the analysis by Varonis, the attack can happen before any application code runs. No vulnerable extension and no mistake in your CMS is required. Per Varonis, PHP versions back to 5.4 are affected, most severely Apache with mod_php.

The German BSI has issued a cybersecurity warning at level 3 / orange and advises disconnecting web servers from the internet until patched if in doubt, as ZDFheute reports. Several authorities and municipalities switched off services as a precaution.

The time pressure is real, but there is no reason to panic. Security firms reported attack attempts early. According to Hostinger, no publicly confirmed successful break-in was known up to 26 October. That is a window of time, not a free pass.

For PHP 8.1 and older branches there are no official releases. According to Red Sift, backports exist only as source code or through vendors and distributions. PHP 8.2 receives no security fixes after 31 December 2026.

If you cannot update right away, the PHP advisory lists interim measures, such as session.upload_progress.enabled=0 in the configuration plus a restart of the workers. They reduce the risk for individual attack paths but do not make an installation safe. Only the update fully solves it.

Node.js: the release of 21 October

The same day, the Node.js project published security releases for the 26.x, 24.x and 22.x lines. They fix ten flaws. The corrected versions are 22.23.4, 24.22.1 and 26.12.1.

The most serious is CVE-2026-111497, an out-of-bounds write in the Brotli decoder that can allow remote code execution. The project rates it high. Others, such as CSA Singapore, rate it critical at CVSS 9.8. Applications that accept Brotli-encoded data are affected. In addition there is, among others, a bypass of TLS hostname verification for IP addresses written in fullwidth digits (CVE-2026-105483, affects 26.x and 24.x).

This is not PHP2Shell, but a separate release with separate flaws. The media use the name Node2Shell, which is not an official name. Whether your application is actually exploitable depends on whether it processes Brotli data. You should install the update anyway. For older lines, the project names no fixes in this release.

The two flaws at a glance

PHP2ShellNode.js October release
IdentifiersCVE-2026-109618, CVE-2026-109619ten CVEs, most serious CVE-2026-111497
Ratingcritical, CVSS 4.0 9.2high according to the Node.js project
Impactcode execution without logincode execution possible with Brotli data
Patched in8.5.12, 8.4.27, 8.3.36, 8.2.3522.23.4, 24.22.1, 26.12.1
Older versions8.1 and older without official releasefixes only for lines 22, 24, 26
Published21 October 202621 October 2026

What operators should check now

  1. Build an inventory. Where does PHP run, where Node.js? Think of website, shop, intranet, Nextcloud, old internal tools and devices with a web interface. Bundled software counts too, as Varonis also notes.
  2. Patch internet-facing systems first. Systems reachable from outside take priority.
  3. Really check the version. With php -v and node -v, in the environment that serves the requests. The command line can differ from the web server version. With containers, updating the host is not enough: pull images again and redeploy.
  4. Ask your host and providers in writing. Was it patched, to which version, and since when?
  5. Clean up after patching. If the server was reachable before the update, credentials and tokens in memory are considered potentially compromised, according to Varonis. Rotate passwords, keys and tokens. PHP processes that start child processes are a warning sign.
  6. Plan for outdated versions. Migrate PHP 8.1 and older now, PHP 8.2 by year end.

Our view from practice

As an IT service provider we see a pattern in this case that goes beyond PHP2Shell: the runtime beneath the application is easily forgotten. This is our assessment:

  • Clarify responsibility. Anyone who commissioned a website should know who patches the runtime: service provider, host or nobody. It belongs in the maintenance contract.
  • Plan for emergency patches. When only hours separate a patch from attack attempts, you need a fixed process with named owners, also outside office hours.
  • Keep backups separate. After a takeover, a backup only helps if attackers cannot delete it too. More in Backup against ransomware.
  • Do not forget remote access. The same pattern applies to VPN gateways, see Securing remote access.
  • Know your obligations. Anyone who commissions software should put patch commitments in the contract. Background is in the article on the Cyber Resilience Act.

For questions on inventory, operations and updates, server infrastructure and IT consulting can help.

Share

Frequently asked questions

  • Probably yes, if your website, shop or an internal tool runs on PHP. According to Varonis, PHP versions back to 5.4 are affected. Patched versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Ask your host or provider which version is running.

  • No. The flaws are in the PHP runtime beneath the application. A current CMS does not protect you if the PHP underneath is not updated.

  • No. They are separate releases with their own vulnerabilities. Both appeared on 21 October 2026. For Node.js the corrected versions are 22.23.4, 24.22.1 and 26.12.1.

Author of this article

AK

Alexander Kreitmair

Co-Founder & Infrastructure

Certified systems integration specialist. Makes sure the systems keep running - servers, networks, deployment pipelines.

This article is for general information only and does not replace individual legal, tax, or business advice. Prices, timelines, and assessments are non-binding estimates provided without guarantee.