08Chronology
Forty-eight hours,
laid out flat.
A wave is not a list. It is a sequence: disclosure, scanning, exploitation, and a second disclosure that lands while responders are still triaging the first.
21 October
2026 · 6 disclosures06:10
UTC
criticalWeb server01PHP2Shell
A hole in the runtime behind roughly 70% of the web
09:30
UTC
criticalCertificate authority02eMudhra root keys
The keys that prove a website is real were cracked
15:00
UTC
criticalData breach03California student data
Every public school student since 2023, including disability status
18:20
UTC
criticalHosting04Railway
Customer secret keys stolen from a hosting platform
20:00
UTC
criticalHosting05Zeabur
321,810 accounts breached; the company is shutting down
22:10
UTC
criticalSupply chain06LiteLLM
An AI package downloaded 3.4 million times a day, poisoned
22 October
2026 · 7 disclosures00:00
UTC
criticalWeb server01GitLab Onigmo RCE
A 10-out-of-10 hole in every self-managed version since 2014
03:30
UTC
highState actor02Cairn
An AI hacking tool broke into 100+ companies
05:00
UTC
highRansomware03Ahold Delhaize
The owner of Food Lion and Stop & Shop knocked offline
07:40
UTC
criticalHosting04Onamae
Malware planted on up to 26,739 customer servers in Japan
09:00
UTC
highBanking05State Bank of India
India's biggest bank confirms a data breach
11:00
UTC
highSupply chain06OVHcloud tooling
Hackers slipped a password stealer into a cloud company's official tool
13:30
UTC
highEndpoint07Siemens
A software hole being used to spread malware
23 October
2026 · 1 disclosuresWhy the order matters
Responders triage in the order things arrive, which is almost never the order of personal relevance. PHP2Shell landed first and dominated attention; the eMudhra root landed second and was the only one that could silently mint a trusted certificate for every domain. The timeline is a reminder that volume is not the same as impact.