Skip to content
Cybersecurity 5 min BellosatoTech Security Team

PHP2Shell, GitLab, Node.js and NGINX: October 2026 vulnerabilities

In brief

The October 2026 PHP2Shell, GitLab, Node.js and NGINX cases show why a working website is not necessarily secure. Services, data and customer trust may be affected. Alongside the 14 and 21 October patches, PHP issued a 23 October advisory about a separate, uncommon case awaiting a fix: actual exposure needs checking, without confusing it with an intrusion that has already happened.

What to do now

  1. Have the technical lead check whether the website and its services use affected components.
  2. Ask for confirmation that fixes are applied and important functions still work.
  3. If there are anomalies, also request an investigation into possible consequences.

Your website opens, the catalogue works and customers send enquiries. Does that mean everything is secure? Unfortunately not: a vulnerability can exist in the software behind the website without causing any visible faults.

The October 2026 alerts affecting PHP, GitLab, Node.js and NGINX are a reminder that security does not end when a website goes live. Leaving maintenance to chance also exposes the business that website represents.

Four real cases, one message for businesses

PHP2Shell: two critical PHP flaws can let an attacker make a server execute instructions without logging in. The problem is in the underlying software: updating only pages or plugins is not enough. Fixes have been available since 21 October. ENISA advisory.

GitLab: it is not normally the software serving pages to visitors, but a platform for managing code, development and project deployment. Fixes for a critical flaw were released on 21 October 2026. Organisations hosting GitLab themselves need to check the patches; GitLab.com has already been patched. Protecting a website also means considering the tools used to build and update it. GitLab bulletin.

Node.js: the 21 October updates fix several issues, including one that can allow code execution while processing compressed data. Modern technology needs maintenance too. Node.js advisory.

NGINX: the 14 October 2026 updates fix issues affecting particular web server configurations. Risk is not the same for every installation: what actually runs must be checked, rather than relying on the product name alone. NGINX advisories.

These are separate issues, not four names for the same attack. An advisory does not prove that every affected system has already been breached.

The fixed versions, at a glance

References checked on 23 October 2026, to be read alongside the bulletins linked above:

  • PHP: 8.2.35, 8.3.36, 8.4.27 and 8.5.12 for the two PHP2Shell flaws fixed on 21 October.
  • GitLab: 19.5.1; the bulletin also lists patches for earlier release lines.
  • Node.js: 22.23.4, 24.22.1 and 26.12.1.
  • NGINX Open Source: 1.30.6 and 1.31.7 for the issues discussed; NGINX Plus has its own releases.

These are reference releases for these flaws, not instructions to switch versions blindly. A technician must check the release line in use, the configuration and any provider-confirmed fixes.

23 October update: another PHP advisory

PHP has reported another scenario that could allow code execution on a server, identified as CVE-2026-115560. It involves the feature that stores upload progress in a session, but requires an unusual combination of configuration and application code: it does not mean that every PHP website is vulnerable to this new issue.

While a fix is prepared for the regular release cycle, PHP suggests temporarily disabling that feature on affected systems. The technical lead or hosting provider should assess and apply the change. This is separate from the two PHP2Shell flaws addressed on 21 October: the patches already available for those flaws remain necessary. Official PHP advisory of 23 October.

30 October update: what we know about attacks

On 26 October, CISA added CVE-2026-109618 and CVE-2026-109619 to its catalogue of exploited vulnerabilities. This is a concrete reason to prioritise fixes, not proof that every exposed website has been breached. Official CISA catalogue.

A researcher documented 35 shell executions across three honeypots, deliberately vulnerable systems used to observe attacks. These are not 35 compromised businesses. Likewise, a collection of investigative indicators does not automatically count victims or successful intrusions. Original research of 24 October.

A separate update: on 26 October, PHP released Windows packages with a -1 suffix to fix a Brotli vulnerability. This is not the fix for CVE-2026-115560, still planned for the regular release cycle according to the advisory checked on 30 October. Official PHP archive.

For a business, the practical lesson is to verify patches and have evidence examined if anomalies appear. A suspicious request or server error alone does not establish a compromise.

What a business could lose

Imagine a shop taking orders through its website. An incident is not just a page that needs repairing:

  • Sales and enquiries: an outage can interrupt purchases, bookings and quotation requests.
  • Data and operations: if an attacker reaches information or credentials accessible to the server, customer records, orders and connected databases may also be affected.
  • Trust: altered content, fraudulent messages or redirects can make a trustworthy business look unreliable.
  • Time and money: restoring services, investigating what happened and reassuring customers can take much more work than planned maintenance.

Not every vulnerability causes these outcomes. The damage depends on exposure and available permissions. The flaws discussed are not all database defects, but a compromised application can become a route to data when systems are not adequately separated.

“We have hosting and a padlock”: why that is not enough

HTTPS protects the connection; it does not fix software. A provider may manage the server while someone else is responsible for the application and add-ons: it must be clear who updates what and how the result is verified.

Even a mostly static website can have forms, control panels or external services to protect. Reducing dynamic components helps, but does not replace maintaining the ones that are needed.

Prevention takes planning, not blind updates

Professional work starts with what is actually there: the website, hosting, software, access rights and data. That establishes priorities, so fixes can be applied under controlled conditions and important functions checked afterwards.

Recoverable backups, limited permissions and monitoring complete the defence. A firewall can help contain some attempts, but cannot replace a patch. If a critical flaw cannot be fixed promptly, the technical lead should assess temporary restrictions on exposed services.

What if unauthorised access has already happened? Updating does not automatically undo an intrusion: what was changed or taken also needs to be investigated.

Two common questions

Should a small business be concerned too?

Yes, without panic. Automated attempts can reach small websites too: exposure matters, not just how well known the business is. A detected attempt, however, is not the same as a successful intrusion.

Do I need to rebuild the website from scratch?

Not necessarily. Sometimes updates and targeted fixes are enough; sometimes an outdated structure needs rethinking. An assessment helps avoid both inadequate repairs and unnecessary rebuilds.

Protecting your website protects customer relationships

At BellosatoTech, we examine website code, configurations and workflows to identify concrete risks and propose proportionate measures, preserving usability and access to public content.

There is no need to wait for the website to stop working. If you do not know who looks after its security, start with a technical website audit: understanding where action is needed is the first step towards protecting data, continuity and trust.

BellosatoTech

Need a secure website with stronger visibility?

We design websites with layered protection against hacking attacks to reduce risk and limit their impact. We also provide anti-bot contact forms, security audits and SEO/AEO programs tailored for business growth.

website security PHP2Shell data protection website maintenance