1. Red
  2. Learn
  3. Landscape and analysis

2026 Cyber Incidents Timeline: Dated, Sourced, Updated

A dated 2026 cyber incidents timeline for September to October: PHP2Shell, GitLab, LiteLLM, Railway, Plex and more, each with its primary source and status.

By Timothy Lindblom, FounderPublished 2 November 20269 min readHow we check facts
On this page
  1. What happened, in date order?
  2. Which incidents are on the timeline, and what does each source say?
  3. Why do the dates on one incident disagree?
  4. Which of these were confirmed exploited, and which were not?
  5. What do the LiteLLM windows tell you?
  6. Which incidents need a patch, and which need a rotation?
  7. Where are the plugin, framework and npm incidents?
  8. Can a scan tell me whether any of this affects me?
  9. What did we leave out?

The main 2026 cyber incidents on this page run from 1 September to 31 October 2026. They are separate events with separate fixes: software bugs (PHP2Shell, GitLab, Node.js, Plex, Ivanti, Cisco), a poisoned release (LiteLLM), platform and account breaches (Railway, Zeabur, PingCAP, Capcom), and a certificate authority failure (eMudhra). Find the rows that match what you run, then open the source.

FactDetailSource
Window covered1 September to 31 October 2026. Earlier 2026 incidents are not on this page yetthis page
Rows15 incidents, each with a date, status label and primary sourcebelow
Highest CVSS in the list10.0 (GitLab CVE-2026-110264); 9.2 for both PHP2Shell CVEs (CVSS v4)GitLab, php.net
Added to CISA KEV in the listIvanti Connect Secure (13 and 30 October); Plex (4 CVEs, 20 October); Collabora Online (23 October); PHP2Shell (2 CVEs, 26 October); Brotli from the Node.js release (27 October); Cisco ASA and FTD (29 October)KEV data file
Last full check2 November 2026this page
15incidents listed with a primary source
6rows with a KEV listing
9.2CVSS v4 for both PHP2Shell CVEs

What happened, in date order?

The timeline below places each event on the day its primary source dates it. Several things happened on 21 October, and the last week of the month brought a run of KEV listings, PHP2Shell among them.

Timeline of October 2026 incidents from 5 October to 30 October 30 Oct Ivanti chain in KEV 29 Oct Cisco ASA and GitLab in KEV; UpdraftCentral update 27 Oct Chrome root removal; Adobe and Brotli in KEV 26 Oct PHP2Shell in KEV 5 Oct Tor relay notice 14-15 Oct Zeabur breach 17 Oct eMudhra report; AWS honeypot attempts 19 Oct Plex update; PingCAP report 20 Oct SafePay advisory; Plex in KEV 21 Oct PHP2Shell, GitLab, Node.js, LiteLLM, Railway 22 Oct Railway tokens reset; Capcom and eMudhra notices 23 Oct PHP follow-up CVE; Collabora in KEV Dates as given by each primary source, checked 2 November 2026.
October 2026 events on the day each primary source dates them. The Zeabur, PingCAP and Tor intrusions began earlier than their disclosure dates; the table gives both.

Which incidents are on the timeline, and what does each source say?

Status labels used in the last column: Confirmed exploited means a primary source says so. Attempts seen means attempts were observed, not that any worked. Vendor-claimed means the affected company's own report. Not reported means the source is silent, which is not proof of no exploitation.

IncidentWhat it isKey datesFix or actionStatus at 2 NovSource
PHP2ShellTwo unauthenticated RCE bugs in PHP core, CVE-2026-109618 and CVE-2026-109619, CVSS v4 9.2. A separate 23 Oct notice covers CVE-2026-115560 (session upload progress, which PHP calls an unlikely RCE vector)Attempts from 17 Oct; disclosed 21 Oct; KEV 26 OctPHP 8.5.12, 8.4.27, 8.3.36, 8.2.35 or a vendor backport; restart workers. For the 23 Oct CVE, PHP advises disabling session.upload_progress.enabledConfirmed exploited: both CVEs in KEV since 26 Oct. CISA added Linux kernel CVE-2026-46300 on 28 Oct, which its entry says chains with them to plant webshells as rootphp.net, KEV data
GitLabCVE-2026-110264, CVSS 10.0, unauthenticated code executionPatched 21 Oct; newer builds 29 Oct18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3, 19.5.1; the 29 Oct builds (19.5.3, 19.4.5 and the rest) are the latestNot in KEV; two detections published. Its sibling regex bug CVE-2026-97229, fixed 12 Oct, entered KEV on 29 OctGitLab
Node.jsSeveral CVEs, four rated High, including a Brotli decoder RCE (CVE-2026-111497)Released 21 Oct; Brotli in KEV 27 Oct22.23.4, 24.22.1, 26.12.1; Brotli 1.2.1 for other software that bundles the decoderConfirmed exploited for the Brotli flaw (KEV, listed under Google Brotli). The other Node.js CVEs are not in KEVNode.js
Plex Media ServerFour CVEs that chain to code executionPublic proof of concept 16 Oct; update 19 Oct; KEV 20 Oct1.43.3.10861 or laterConfirmed exploited (Plex; CISA KEV)Plex
Collabora OnlineCVE-2026-110447, OS command injection in the built-in CODE serverAdvisory 14 Oct; KEV 23 OctBuilt-in CODE server 26.4.303 or laterConfirmed exploited (CISA KEV)Collabora, CISA
LiteLLM 1.107.0Malicious PyPI and container artifactsWindows on 21 Oct (below); signing key rotated 23 OctRebuild, pin 1.106.2 or earlier (Enterprise proxy: 1.106.5) or a release from 24 Oct on, rotate what the host could readVendor-claimed intrusion; contained, investigation open at the 30 Oct updateLiteLLM
RailwayAccess to systems storing customer environment variablesDisclosed 21 Oct; tokens reset 22 Oct; resolved for existing users 26 OctRotate every stored variable; create new API tokensVendor-claimed; at most 1.85% of workspaces; more than 100,000 users hit by upstream key resetsRailway
TiDB Cloud (PingCAP)Stolen service-account credentials used to copy internal data and source code9 Sep to 7 Oct; report 19 OctReplace TiDB Cloud API keys, then revoke the old onesVendor-claimed; no evidence customer database data was affectedPingCAP
ZeaburSecond breach: platform database read, 101 GCP dedicated servers accessed as root14 to 15 Oct; report 19 Oct; wind-down 1 to 31 DecRotate all stored credentials; rebuild affected serversVendor-claimed; 3,218,965 variable records readZeabur
Tor relaysCompromised Linux relay hosts altered to intercept SSHNotice 5 OctOperators audit and reinstall; users verify SSH host keysConfirmed by the Tor Project; scope still openTor Project
eMudhraEight intermediate CA certificates with weakly generated keysReported 17 Oct; exit from global TLS announced 22 Oct; Chrome root removal set for 27 OctReplace emSign certificates; update browser, OS, runtime and container trust storesKeys recoverable; Google reports no CT-logged certificates chaining to the six TLS intermediates before its block. eMudhra is leaving the global SSL/TLS businessGoogle, CSO Online
SafePayRansomware group in joint advisory AA26-293AAdvisory 20 Oct; activity since Aug 2024Patch edge and VPN devices; MFA; tested backupsConfirmed active campaign; 600+ is the authors' estimateCISA
Ivanti Connect SecureZero-day chain: CVE-2026-104935 authentication bypass and code execution, CVE-2026-111357 escalation to root, CVE-2026-118527 file writeKEV 13 Oct; escalation patched 29 Oct; two more CVEs in KEV 30 OctApply Ivanti's fixed build; memory and network forensics, because Ivanti's integrity checker can miss itConfirmed exploited (CISA KEV, Volexity)Volexity
Cisco Secure Firewall ASA and FTDCVE-2026-76418, CVSS 8.6, unauthenticated crash through the Remote Access SSL VPN loginAdvisory 28 Oct; KEV 29 OctFixed releases such as ASA 9.24.1.27 and FTD 7.6.7; interim: remove secondary authentication from tunnel groupsConfirmed exploited (Cisco; CISA KEV)Cisco
Capcom (CAPCOM ID)Unauthorized access to Capcom's membership loginDetected 19 Oct; disclosed 22 Oct; narrowed 23 OctChange reused passwords; treat Capcom-themed email as suspectVendor-claimed; 11,774,247 email and identifier records, 196 passwords changed, 19 store profiles readCapcom

Why do the dates on one incident disagree?

Four different dates get quoted for one incident, and people compare them as if they were the same thing.

Date typeExample from this pageWhat it tells you
Intrusion or activityPingCAP: 9 September to 7 OctoberWhen the attacker had access
DisclosurePingCAP: report published 19 OctoberWhen the vendor told the public
FixPlex: fix in 1.43.3.10861, announced 19 OctoberWhen a fixed build was announced
Exploitation noticePlex: KEV on 20 OctoberWhen an authority said it was exploited

Plex shows the gap well. Plex says a public proof of concept was released on 16 October, its update naming the CVEs and exploitation came on 19 October, and the KEV entry was on 20 October. A reader who only saw the KEV date could think the bug was a day old, when exploit material had been public for four days.

The reverse happens with attempts. AWS says its honeypots saw PHP2Shell attempts on 17 October, four days before the PHP notice. AWS also says it is unclear whether those attempts would have worked on real systems.

Which of these were confirmed exploited, and which were not?

Seven rows carry a source that says exploitation happened: PHP2Shell, Plex, Collabora Online, the Brotli flaw from the Node.js release, Ivanti Connect Secure and Cisco ASA and FTD (all in the KEV catalog), and SafePay (a ransomware campaign in AA26-293A). The platform breaches are confirmed by the companies themselves, which is a different statement: the vendor says an intruder got in.

PHP2Shell shows how fast the label moves. CISA's alert of 21 October said CISA had not observed exploitation at publication, while AWS reported attempts from 17 October. Five days later, on 26 October, CISA added both CVEs to the KEV catalog. GitLab's CVE-2026-110264 was still not listed at our 2 November check, though its sibling CVE-2026-97229 went in on 29 October.

"Attempts seen" and "listed as exploited" describe different evidence. The first is a vendor's sensor data. The second is a government list with its own threshold, and it can lag the first by days.

What do the LiteLLM windows tell you?

The LiteLLM report is precise, and the precision is the useful part; what the poisoned 1.107.0 release did has its own page. LiteLLM says the PyPI package 1.107.0 was live from 11:39 to 13:23 UTC on 21 October, and the Docker Hub tags were affected from 11:46 to 14:20 UTC. The GHCR tags were affected until 13:51 UTC. Earlier versions and the enterprise registry were reported unaffected, and the official source tag was clean. LiteLLM rotated its image-signing key on 23 October, so the bad 1.107.0 images still carry a valid signature from the old key: check images by digest, not by signature.

That scope is narrow in time and in version. If you installed or pulled outside those windows, the report does not place you in the affected set. If you installed inside them, treat the environment as compromised and follow the vendor's steps. Our guide to which credentials to rotate first covers the order.

Which incidents need a patch, and which need a rotation?

This is the question the vendor pages answer separately and no one answers in one place. The action depends on the kind of incident. If you stored variables on Railway, rotating every secret there is the walk-through.

KindRowsWhat you doEvidence that it is done
Software bugPHP2Shell, GitLab, Node.js, Plex, Collabora, Ivanti, Cisco ASA and FTDUpdate to a fixed build, restart the servicePackage or build identifier naming the fix, plus a restart time after it
Poisoned releaseLiteLLMRebuild from scratch, pin an earlier release, rotateOld secrets revoked, new ones deployed
Platform breachRailway, Zeabur, TiDB Cloud, CapcomRotate every credential stored there, check provider logsOld credential revoked at its issuer, new one live
Trust failureeMudhraUpdate trust stores, rebuild stale imagesVendor advisory for your runtime, image rebuilt
CampaignSafePay, Tor relaysHarden access paths, audit hostsVendor or agency checklist completed

For PHP2Shell the fix steps are in patch PHP, restart workers, verify it ran, and the version trap is in the full PHP2Shell write-up. For the whole month as a to-do list, use the checklist for this week.

Where are the plugin, framework and npm incidents?

They have their own pages, with their own primary sources, because each needs its own version check:

Self-hosted GitLab has a separate page on the CVSS 10.0 bug.

For how this month compares with earlier events, see PHP2Shell versus Log4Shell. The wider table of every October incident is in the month's running incident tracker.

Can a scan tell me whether any of this affects me?

Partly. The free scan reads the stack your site serves and matches each version to known vulnerabilities, so it can tell you a version looks affected. It is a lookup. It cannot see a vendor backport, which runtime serves a virtual host, whether workers restarted, or which platform holds your keys.

That puts most readers in the unknown state for most rows. Moving to confirmed needs evidence from the server, the host or the vendor: the build identifier that names the fix and a restart or redeploy after it, or an old credential revoked and a new one deployed. The platform rows (Railway, Zeabur, TiDB Cloud, LiteLLM) are about what you stored, so no outside scan can answer them. You answer them from your own inventory.

What did we leave out?

We leave out claims that spread with these incidents and that no primary source supports. These include data volumes and extortion figures for platform breaches, victim counts presented as audited lists, named victims, and origin stories for bugs based on how old the oldest affected version is. We did not list Japan's government advisories because their pages did not load at our 24 October check, so we cannot cite them today. We will add that row once a primary page can be read.

A fact goes on this page when a vendor advisory, CVE record, CISA entry or status page says it, with the link next to it. Everything else stays a lead. If a source we cite has changed, write to support@run.cloud and we will re-check it.

Questions people ask

What were the biggest cyber incidents of 2026?

This page covers 1 September to 31 October 2026 only, and it does not rank by size. The sizes in vendor reports are the vendors' own estimates, and a count of records says little about harm to you. The ones with a primary source saying they were exploited are PHP2Shell, Plex, Collabora, the Brotli flaw, Ivanti Connect Secure, Cisco ASA and FTD, and the SafePay campaign.

Is it true the whole internet is being hacked in 2026?

No primary source says that. The record shows separate incidents with separate causes and fixes: software bugs, poisoned releases, platform breaches and one certificate authority failure. Each row on this page says who is affected and what the source says about exploitation.

Which of these incidents are confirmed as exploited?

CISA lists PHP2Shell (since 26 October), Plex, Collabora Online, the Brotli decoder flaw, three Ivanti Connect Secure CVEs and Cisco ASA and FTD in its Known Exploited Vulnerabilities catalog. SafePay is an active ransomware campaign in a joint advisory. GitLab CVE-2026-110264 is not listed, though its sibling CVE-2026-97229 is.

How do I know whether one of these affects me?

Match the rows to what you run and what holds your secrets. A software row applies if you run a version below the fix. A platform row applies if you stored credentials there. From outside, a scan can read versions but cannot see backports, restarts or which platform holds your keys.

Do I need to change my passwords after these breaches?

Only for the ones that hold your credentials: LiteLLM 1.107.0, Railway, Zeabur, TiDB Cloud API keys, and a CAPCOM ID password you reuse elsewhere. Rotate what the affected host or platform could read, starting with provider keys and database passwords. The software bugs in the table call for updating, not for rotation.

How often is this timeline updated?

The date at the top changes when a row changes, not for formatting edits. Each row carries the date we last checked its primary source. Vendor pages move quickly, so open the linked source before you act on a version number.

Sources

  1. PHP security notice, 21 and 23 October 2026 (php.net)PHP2Shell CVEs, fixed releases, the 23 October notice for CVE-2026-115560 and the 26 October Windows rebuilds. Checked 2 November.
  2. CISA alert: Critical Vulnerabilities in PHP Require Immediate Patching (21 October 2026)Says CISA had not observed exploitation at publication. Checked 24 October.
  3. AWS Security Blog: PHP2Shell exploitation seen in MadPot honeypots before disclosureVendor telemetry. Checked 24 October.
  4. CISA Known Exploited Vulnerabilities catalogLists PHP2Shell, Plex, Collabora, Brotli, Ivanti and Cisco ASA entries. Did not list GitLab CVE-2026-110264 at our 2 November check.
  5. CISA KEV data file (cisagov/kev-data, CSV)Dates added for every KEV row on this page. Read 2 November 2026.
  6. CISA alert: one vulnerability added to the KEV catalog (23 October 2026)CVE-2026-110447, Collabora Online built-in CODE server, OS command injection.
  7. GitLab critical patch release 19.5.1 (GitLab Docs, 21 October 2026)CVE-2026-110264, CVSS 10.0, two detections published. Checked 2 November.
  8. Node.js October 2026 security releasesFour rated High, fixed in 22.23.4, 24.22.1 and 26.12.1. No later addenda at our 2 November check.
  9. Plex security update (Plex forums, 19 October 2026)Four CVEs, fixed in 1.43.3.10861, exploitation reported by Plex. Checked 24 October.
  10. CISA KEV additions, 20 October 2026
  11. CISA advisory AA26-293A: SafePay ransomware (20 October 2026)The 600 organisations figure is the advisory authors' estimate. Checked 24 October.
  12. LiteLLM incident report (21 October 2026)Vendor account. Header still reads 21 October 20:30 UTC; updates added on 23 and 30 October. Checked 2 November.
  13. Railway security disclosure (21 October 2026)Two follow-up posts on 23 October about restoring deployments.
  14. Railway preliminary report: Oct 21st security incident (22 October 2026, updated 26 October)Scope estimate of at most 1.85% of workspaces; resolved for existing users on 26 October.
  15. Railway status incident QH8L8B3E
  16. PingCAP security update, October 2026Published 19 October. No update since, at our 2 November read.
  17. Zeabur preliminary incident report (19 October 2026)
  18. Zeabur shutdown notice (17 October 2026)
  19. Tor Project: relays security incident (5 October 2026)
  20. Mozilla: protecting Firefox users after the eMudhra intermediate compromise (20 October 2026)
  21. Google Security Blog: protecting Chrome and Android users from the eMudhra intermediatesReport time 17 October 18:05 UTC; Chrome Root Store removal set for 27 October.
  22. CSO Online: eMudhra quits global TLS certificate market (23 October 2026)Reports eMudhra's 22 October press note on leaving the global SSL/TLS business.
  23. Collabora GHSA-g3vx-3m76-fghh (14 October 2026)CVE-2026-110447, fixed in built-in CODE server 26.4.303.
  24. Volexity: chained exploitation of Ivanti Connect Secure zero-days (13 October 2026, updated 29 October)
  25. Cisco advisory cisco-sa-asaftd-tunnel-dos-s6mgkb75 (28 October 2026)CVE-2026-76418, exploited, fixed releases and the secondary-authentication mitigation.
  26. Capcom: notice on unauthorized access (22 October 2026, updated 23 October)
  27. CERT-In advisory CICA-2026-3649 (eMudhra)

Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.