Threat researchCisent
Black October: everyone is vulnerable
In two weeks, PHP, GitLab, Node.js, nginx, a key AI library and a certificate authority all failed at once. It was not a coordinated attack: it is the new pace, and no one is left out.

Updated October 25: the Node.js flaw is in Brotli, a Google library that other programs use too. That is why there is more to update than Node (see “What to do this week”).
The press and LinkedIn gave the second half of October 2026 a name: “Black October”.12 It is not an official name, and it is not a campaign. It is a run of critical flaws and attacks, almost all at once, in pieces nearly every organization uses: the language of the web, the web server, the code repository, the AI libraries, the certificates and the cloud. On October 21 alone, PHP, GitLab and Node.js shipped emergency patches, and a widely used library for connecting applications to AI models woke up with malware.
What happened, day by day
- Early October: Tor. Attackers controlled 333 Tor exit relays and diverted SSH connections to 12 trap servers, which captured passwords in transit. The relays were flagged as malicious on October 4, and the researcher who found them disclosed it on the 20th.3
- October 14: nginx. F5 shipped out-of-band patches for the nginx web server.4 Three of the flaws score 9.2 out of 10: an attacker with no credentials can restart the server’s processes and, in certain configurations, run code. Affected versions go up to 1.30.5 and 1.31.6.5 We covered it here.
- October 17: the first shot. Amazon’s honeypots recorded the first attempt to exploit PHP2Shell, four days before the patch. Amazon still doesn’t know where the attacker got the details.6 That same night, Mozilla was told that the private keys of eight intermediate certificates from the eMudhra certificate authority were compromised, and it blocked them in Firefox in under three hours.7 eMudhra says a step in its key ceremony produced a second, weak set of keys alongside the good ones, and that those certificates never issued a single one.8 The same day, one day after the flaw was published, attacks began on unpatched Plex servers to turn them into cryptocurrency miners.9
- October 20: a Japanese cloud. GMO Internet confirmed malware on customer servers of Onamae.com Desktop Cloud, a service for running trading bots. Up to 26,739 servers may have been exposed. GMO shut them all down the next day, and on the 22nd a Japanese forex broker delayed its customers’ withdrawals.10
- October 21: the black day.
- PHP2Shell: two flaws in PHP’s core, scored 9.2 out of 10, let an attacker take over a server without a password. They affect every version since 5.4.11 Chile’s national CSIRT issued alert AVC26-00740 that day.12 We covered it in detail here.
- GitLab: a 10-out-of-10 flaw lets an attacker run code without logging in on self-managed GitLab servers, from version 7.0 onward.13
- Node.js: ten flaws; the worst, in the Brotli decompressor, can lead to remote code execution.14 The flaw is not Node’s alone: it is in Brotli, Google’s compression library, in versions 1.0.3 through 1.2.0, and it reaches other programs that use it, such as curl. Google fixed it the same day, in versions 1.0.10, 1.1.1 and 1.2.1.1516
- LiteLLM: version 1.107.0 of this library, which connects applications to AI models, shipped with credential-stealing malware. It was on PyPI for close to two hours, and on Docker Hub until 14:20 UTC.17
- Railway: a third party may have accessed its customers’ encrypted environment variables, and obtained the decrypted contents of some. The platform paused all deployments and asked everyone to rotate every key.18
- On top of that, the FBI and CISA warned about the SafePay ransomware, with more than 600 victims: we covered it here.
- October 22 and 23: the accounts and the code. Capcom reported access to 11,774,247 records of its account service, and 196 passwords changed without permission.19 Six reports of Linux kernel flaws, still unpatched, reached the developers’ public mailing list by mistake; two allow remote code execution.20 Big US banks found AI agents operating inside customer accounts, almost always with the password the customer handed over (our note).21 And the PHP team warned of a third flaw, in session handling and still unpatched, that in certain configurations reaches even servers that were already updated.12
In those same days, a Signal flaw came to light that could leave the microphone, and perhaps the camera, on after hanging up, if the attacker was already on the call. It is fixed in current versions.22 And in California, someone used a stolen credential to get into the file site of the organization that runs the state tests, and copied data on public school students from the last three school years.23
AI, on both sides
PHP2Shell was found by Wiz researchers with help from AI models, which they used to find the flaws, write the test exploits and validate the patch. According to Wiz, a single researcher did in a week what used to take a world-class team months.11
The Brotli flaw was reported by Codex Security, OpenAI’s AI agent that looks for flaws in code.1424
The same speed runs the other way. The first attack attempt came before the patch.6 Railway believes its incident is part of a series of attacks on platforms, aimed at reaching AI inference providers.18 And a few days ago we covered an attacker who left AI agents attacking on their own.
Nor is the volume about one month. NIST’s vulnerability database lists 88,602 published in 2026 as of October 24, against 49,972 in all of 2025. As OpenSecurity puts it, AI finds flaws faster than ever, and patching is still on us.1
Why “everyone is vulnerable”
None of these flaws needed a user’s click. They were in what nearly every organization shares without knowing it, and what nobody looks at until it fails.
Three things changed this month:
- The attack no longer waits for the patch. With PHP2Shell, it came four days early.6
- A patch no longer closes the matter. PHP’s third flaw reaches servers that had already been updated.12
- It is no longer clear who is acting. A bank can’t always tell whether the account is being run by the customer, by an agent the customer authorized, or by an attacker.21
What to do this week
- PHP: upgrade to 8.5.12, 8.4.27, 8.3.36 or 8.2.35, and ask your hosting provider who handles it. Until the third flaw is patched, Chile’s CSIRT recommends setting
session.upload_progress.enabled=0.12 - Self-managed GitLab: 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3 or 19.5.1.13
- Node.js: 22.23.4, 24.22.1 or 26.12.1. Unsupported versions get no fix.14
- Brotli: update the library on servers and computers to 1.0.10, 1.1.1 or 1.2.1, or with your distribution’s patch: Debian has already published it for versions 12 and 13. If your Node uses the system’s Brotli, like Debian’s or the one Homebrew installs on a Mac, updating Node is not enough.1516
- nginx: the newest version of your branch; affected versions go up to 1.30.5 and 1.31.6.5
- LiteLLM: if you installed 1.107.0, assume the keys are gone: rebuild the environment, pin 1.106.2 and rotate everything that machine could reach.17
- Railway: rotate every environment variable, API keys included.18
- Plex: 1.43.3.10861 or later, and don’t expose port 32400 to the internet.9
- Your logs: review them from October 17, not from the date of the advisory.12
What is still unknown
- How the attacker had the PHP2Shell details four days before the advisory.6
- How much was really exploited: Amazon speaks of broad exploitation, while other analysts see mostly scanning and exploits that don’t work.6
- How many of GMO’s 26,739 servers were actually compromised.10
- Whether the California students’ data has been published. The organization says it has found no evidence of that.23
Where Cisent comes in
In a month like this, the question isn’t whether any of it touches you, but whether you find out in time. There are two ways to get there first: find what’s exposed before the attacker does, and see the attack while it happens.
Sentinel Red Team attacks the organization’s systems with its authorization and within the scope it defines, to find the gaps before an attacker does: the admin panel exposed on a server nobody watches, the service published by mistake, the insecure configuration. It’s ongoing testing, not one audit a year, and every new attack pattern helps train the defense.
Sentinel Defense detects, assesses and blocks attacks in real time alongside the EDR, the firewall and every connected source, with connectors for FortiGate, pfSense, OPNsense, UniFi and more. It acts on its own only where an action can be undone, such as blocking an attacking IP or an intrusive connection, and asks before anything with impact. Every new attacker technique becomes a defense rule.
Sources
David Carrero Fdez-Baillo, OpenSecurity, “‘Octubre negro’: las CVE publicadas en 2026 ya casi duplican todo 2025” (in Spanish), October 24, 2026, with data from the NVD API 2.0 (NIST). https://www.opensecurity.es/octubre-negro-cve-2026-nvd-record-vulnerabilidades↩︎
Axios, “Black October: why bugs discovered by OpenAI tech are creating a cyber emergency”, October 22, 2026. https://www.axios.com/2026/10/22/php-vulnerability-security-update-websites↩︎
Florian Burnel, IT-Connect, “Tor Network: 333 Compromised Exit Relays Intercepted SSH Connections to Spread Ebury”, October 23, 2026. https://www.it-connect.tech/tor-network-333-compromised-exit-relays-intercepted-ssh-connections-to-spread-ebury/↩︎
F5, “Out-of-band Security Notification (October 14, 2026)”, K000163408. https://my.f5.com/manage/s/article/K000163408↩︎
Cyber Security Agency of Singapore, “Critical Vulnerabilities in F5 NGINX Products” (AL-2026-150), October 21, 2026. https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-150/↩︎
BleepingComputer, “Amazon says PHP2Shell exploitation began 4 days before patches”, October 22, 2026. https://www.bleepingcomputer.com/news/security/amazon-says-php2shell-exploitation-began-4-days-before-patches/↩︎
Mozilla Security Blog, “Protecting Firefox users following the compromise of eMudhra intermediate certificates”, October 20, 2026. https://blog.mozilla.org/security/2026/10/20/protecting-firefox-users-following-the-compromise-of-emudhra-intermediate-certificates/↩︎
eMudhra, statement on its certificate security incident, October 20, 2026, updated October 22. https://emudhra.com/en/post/certificate-security-incident↩︎
SecurityOnline, “Plex2Shell Exploited in the Wild: PoC Released for Unauthenticated Plex Media Server RCE Chain”, October 19, 2026. https://securityonline.info/plex2shell-plex-media-server-exploited/↩︎
FinanceFeeds, “GMO Says 26,739 Cloud Servers May Be Exposed in Cyberattack, OANDA Pauses Withdrawals”, October 22, 2026. https://financefeeds.com/gmo-says-26739-cloud-servers-may-be-exposed-in-cyberattack-oanda-pauses-withdrawals/↩︎
Wiz Research, “PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet”, October 21, 2026. https://www.wiz.io/blog/php2shell-php-rce↩︎
CSIRT Nacional (Chile), “PHP - Vulnerabilidad Crítica” (AVC26-00740, in Spanish), October 21, 2026, updated October 23. https://csirt.gob.cl/alertas/avc26-00740/↩︎
CERT-EU, “Security Advisory 2026-019: Critical Vulnerability in GitLab Community and Enterprise Editions”, October 22, 2026. https://cert.europa.eu/publications/security-advisories/2026-019/↩︎
Node.js, “Wednesday, October 21, 2026 Security Releases”, October 21, 2026. https://nodejs.org/en/blog/vulnerability/october-2026-security-releases↩︎
Google, “Releases · google/brotli”: versions 1.2.1, 1.1.1 and 1.0.10, October 21, 2026. https://github.com/google/brotli/releases↩︎
Debian, “CVE-2026-111497”, Debian Security Tracker. https://security-tracker.debian.org/tracker/CVE-2026-111497↩︎
LiteLLM, “Contained: Oct 21, 2026 LiteLLM release v1.107.0 Compromised”, October 21, 2026, with notes from October 23. https://docs.litellm.ai/blog/security-incident-oct-21-2026↩︎
Railway, “Security Disclosure: Wednesday October 21st”, October 21, 2026. https://blog.railway.com/p/security-disclosure-wednesday-october-21st↩︎
Help Net Security, “Capcom data breach exposes 11.7 million account records”, October 23, 2026. https://www.helpnetsecurity.com/2026/10/23/capcom-id-data-breach-11-million-records-exposed/↩︎
Phoronix, “Several Linux Kernel Vulnerabilities Accidentally Posted To Public Kernel Mailing List”, October 22, 2026. https://www.phoronix.com/news/LKML-New-Trend-Vulnerabilities↩︎
CBS News, “AI agents are roaming around consumers’ bank accounts, and banks aren’t happy about it”, October 23, 2026, on an Axios report from October 22. https://www.cbsnews.com/news/ai-agents-customer-bank-accounts-security/↩︎
Security Affairs, “Signal Vulnerability Could Keep Calls Alive After Users Hang Up”, October 22, 2026. https://securityaffairs.com/201490/security/signal-vulnerability-could-keep-calls-alive-after-users-hang-up.html↩︎
SecurityWeek, “One Compromised Login Exposed Millions of California Students’ Records”, October 2026. https://www.securityweek.com/one-compromised-login-exposed-millions-of-california-students-records/↩︎
Bloomberg, “OpenAI Releases AI Agent Security Tool for Research Preview”, March 6, 2026. https://www.bloomberg.com/news/articles/2026-03-06/openai-releases-ai-agent-security-tool-for-research-preview↩︎