Skip to content
Cybersecurity

Black October 2026: what a SaaS founder needs to do this week

PHP2Shell, a GitLab 10.0, Collabora, VeloCloud, Next.js, two npm worms and Microsoft's record Patch Tuesday, all in one week. A short plan to check your exposure, what to patch first, and what the LGPD requires if it leaks.

What happened

October 2026 became "Black October" because it stacked, within a few days (roughly October 13 to 23), a rare run of critical flaws, several already exploited. It was not one attack, it was a disclosure wave. Here is what matters for anyone running a SaaS, grouped by where it bites.

If you run your own server (VPS, container, on-prem)

  • PHP2Shell (CVE-2026-109618 and CVE-2026-109619). Two flaws in the PHP core, scored 9.2 on CVSS 4.0 per the NVD. Fixed on October 21 in 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Details leaked early and there are reports of exploitation attempts from October 17. If you cannot patch now, one mitigation for the CVE-2026-109619 path is setting session.upload_progress.enabled to Off in php.ini (mitigation, not a fix).
  • GitLab (CVE-2026-110264). Reported October 21 as a 10.0, unauthenticated remote code execution on self-managed instances. If you host your own GitLab, this is the most urgent item on the list.
  • Collabora Online CODE server for Nextcloud (CVE-2026-110447). Command injection, RCE before richdocumentscode 26.4.303. In CISA KEV since October 23, US federal deadline October 26.
  • Arista VeloCloud Orchestrator on-prem (CVE-2026-114625). SQL injection, scored 9.4, also in KEV since October 23.
  • Siemens Software Center (CVE-2026-110936). DLL side-loading, active exploitation confirmed by Siemens.
  • Plex Media Server. Four chained flaws ("Plex2Shell"), the newest activity in the wave, around October 23.

If you run Node or Next.js

  • Next.js. An October 14 disclosure of unauthenticated RCE under use cache configurations, plus a critical flaw in the image optimization pipeline (CVE-2026-96889). Fixed in 15.5.28 and 16.4.1; for the image flaw, also move sharp to 0.35.5+.
  • Node.js (CVE-2026-111497). A Brotli decoder flaw, rated high, can enable RCE in some configurations. Fixed in 22.23.4, 24.22.1 and 26.12.1.

Supply chain (npm)

  • Tensorlake 0.5.144. Compromised on October 8, part of the Shai-Hulud worm family. It shipped through the official release pipeline with valid provenance: a build attestation does not prove a package is safe. It was live for a little over an hour.
  • LiteLLM. A malicious package with a credential stealer (cloud keys, GitHub tokens, .env), pulled within about two hours. If you installed it in that window, treat the machine as compromised and rotate everything.

Microsoft Patch Tuesday (October 13)

A record, around 1,411 flaws per BleepingComputer, with three zero-days.

  • CVE-2026-96951 (exploited). Scored 8.8, in Windows Shell, bypasses Mark of the Web. A detail that made headlines: it was found by Anthropic's Claude AI.
  • CVE-2026-108398. Windows Defender Application Control bypass in .NET, publicly disclosed.
  • CVE-2026-92707. DoS in MessagePack-CSharp, publicly disclosed.
  • Among the criticals: CVE-2026-96934 (Windows DHCP Server RCE, 9.8) and CVE-2026-100202 (MSMQ RCE, 9.8).

CISA KEV (October 14)

Four flaws added for active exploitation, federal deadline October 17: CVE-2026-0322 (Palo Alto PAN-OS), CVE-2026-76519 (Cisco Secure Email Gateway), and CVE-2026-105133 and CVE-2026-105134 (Ahsay AhsayCBS).

Brazil: the privacy angle

The global wave rhymes with the local picture. In October, Lupo disclosed an incident with unauthorized access to its order system between September 18 and 23, exposing name, CPF, email, phone, address and purchase data from 2020 to 2023, and said it notified the ANPD. The practical reminder: if your SaaS stores a national ID and something leaks, the bill is not only technical.

Under Brazil's LGPD, an incident with relevant risk or harm to data subjects must be reported to the ANPD and to the subjects (Resolução CD/ANPD nº 15/2024 governs the process and timing). Fines reach up to 2% of revenue, capped at R$ 50 million per violation. Having a map of where personal data lives, before the incident, is what separates a response from a panic.

Are you exposed?

  • Do you run PHP? WordPress, Laravel, Drupal or any PHP app on a VPS or container. Run php -v on the server and inside the container image, not just on your laptop.
  • Do you self-host GitLab? It is unauthenticated RCE scored 10.0, the most urgent item.
  • Nextcloud Office, VeloCloud, Siemens Software Center or Plex? Each is on the list above.
  • Node/Next? Both Next.js and Node have a fixed release.
  • Installed anything from npm in recent weeks? Check whether you pulled compromised tensorlake or litellm.

If your SaaS is Node, Python or Go with no PHP in the path, PHP2Shell probably does not reach you. "Probably" because plenty of teams forget a WordPress blog or landing page running next to the app.

What to do, in order

  • Patch first what is unauthenticated RCE and already exploited: self-hosted GitLab, PHP, Collabora, VeloCloud, Siemens.
  • Rebuild the container image, not just the server. Updating the host and forgetting the image is the most common mistake.
  • Move Next.js, Node and sharp to the fixed releases.
  • Audit what came in from npm; if you pulled a compromised package, rotate cloud keys, tokens and .env.
  • Check logs since October 13 for odd requests. If you find any, treat it as an incident and rotate the credentials that lived on that machine.
  • If personal data is involved, start the ANPD process.

Let AI help, without panic

Ask your coding agent, read-only, to list where PHP, Next.js and npm dependencies show up in the project and its images, quoting file and line. That is inventory, not an attack.

For a fast automated first scan of your repository, hullcheck (open source, free, read-only) flags the common mistakes that turn into incidents with file and line: a committed secret, a table with no row level security, a webhook with no signature, an injectable GitHub Action. Install it with cargo install hullcheck and run it inside the repo. Then the RET Promptbook ships the triage prompt that separates what to fix now from what needs human validation, plus the personal-data map for the LGPD side.

Sources

  • NVD: CVE-2026-109618, CVE-2026-109619, CVE-2026-110264, CVE-2026-110447, CVE-2026-114625, CVE-2026-110936, CVE-2026-96889, CVE-2026-111497, CVE-2026-96951
  • php.net: releases 8.2.35, 8.3.36, 8.4.27 and 8.5.12
  • CISA Known Exploited Vulnerabilities, additions of 2026-10-14 and 2026-10-23
  • BleepingComputer and Dark Reading: Microsoft October 2026 Patch Tuesday
  • Datadog, Socket and Stingrai: Shai-Hulud npm wave (tensorlake, litellm)
  • Lupo incident and ANPD notification, October 2026 coverage
Tags:#Black October#PHP2Shell#GitLab#Next.js#CISA KEV#npm supply chain#Patch Tuesday#LGPD#ANPD
Gabriel Ferreira
Gabriel Ferreira

Founder & Lead Pentester

Gabriel Ferreira reviews production SaaS with focus on login, billing, data, and evidence founders can act on.

How much does it cost to test your system?

Answer four questions and see the package, price and timeline for your case, no sign-up. We refund 50% if the test finds no flaw.

See price and timeline for my case
Keep reading
View all