Black October 2026: what the October wave actually included
When we say Black October 2026, we mean the October 2026 wave of major cybersecurity incidents, critical software vulnerability disclosures, and AI-accelerated attacks. That is a descriptive label, not the name of a single official U.S. or Texas government campaign. October was also CISA’s Cybersecurity Awareness Month, with the 2026 theme “Securing the Next 250” (CISA, 1 October 2026).
This post is a source-cited briefing for operators in Austin and across Texas. It is not a complete catalog of every October incident, and it is not legal advice.
Three practical threads ran through the month:
- Critical disclosures in widely deployed software, including PHP and GitLab, that needed fast inventory and patching — the work of managed vulnerability management.
- Account-takeover, vishing, and follow-on activity against professional organizations, which is why managed EDR and email / identity controls still matter after a patch is applied.
- Attacks and supply-chain compromises aimed at AI systems and AI credentials, which is why LLM and agent applications should be treated as their own security scope — see our AI-accelerated attacks note.
If you want a first, public-only look at your own internet-facing exposure, request a free external attack-surface snapshot.
Critical disclosures: PHP and GitLab
On 21 October 2026, the PHP project issued a security release for CVE-2026-109618 and CVE-2026-109619, a pair of unauthenticated remote-code-execution vulnerabilities later widely referred to as “php2shell.” Patches were released in PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. CISA issued an alert the same day calling for immediate patching, and on 26 October 2026 added both CVEs to the Known Exploited Vulnerabilities Catalog.
The same month, GitLab published two CVSS 10.0 patches for unauthenticated remote code execution in its CI/CD regular-expression compiler: CVE-2026-97229, in the 12 October 2026 patch release, and CVE-2026-110264, in the 21 October 2026 patch release.
If your organization runs PHP on internet-facing applications, or a self-managed GitLab instance, the first question is still the plain one: are you on a patched version, and do you have a way to know? That is vulnerability management, not a newsletter subscription.
We walk through those disclosures, and a local vendor incident, in more detail in October 2026 critical disclosures and vendor risk.
Major incidents: vendors, professional services, and a local school-system notice
Critical CVEs were only one part of the month.
Frontline Education, a widely used education-software vendor, posted a formal notice of a data breach on 26 October 2026. The company stated that it identified unauthorized access on 14–15 August 2026 affecting certain data in Frontline Central and School Health Management, including Social Security numbers and other identifiers, and that it began notifications around 26 October. Frontline Education official notice.
Austin Independent School District confirmed that staff data in Frontline Central was involved, including names, Social Security numbers, personal and work email addresses, and personal addresses, and that the matter was reported to the Texas Department of Information Resources. KVUE, 26 October 2026.
That is a reminder that a “vendor tool” is still part of your attack surface. Texas organizations also have their own notice clocks under Business & Commerce Code Chapter 521 if a breach of system security involves sensitive personal information — generally individual notice not later than the 60th day after determining a breach occurred, and Attorney General notice not later than the 30th day if at least 250 Texas residents are involved. See our Texas cybersecurity compliance briefing and the official Chapter 521 text.
Separately, September and October brought a cluster of law-firm disclosures and a Canadian government alert on help-desk voice phishing, including Microsoft Teams workflows and attempts to relay or bypass multi-factor authentication. We cover that pattern, and what it means for Texas firms’ ethics duties, in What the 2026 law-firm incidents mean for Austin firms.
AI-accelerated attacks and the AI software supply chain
Two official October reports are especially relevant to organizations that build or consume AI services.
Railway published a preliminary report on 22 October 2026 about an incident that began on 20 October. The company stated that attackers attempted to obtain AI provider API keys for use in distillation attacks, and it described exposure of customer encrypted secrets with guidance on key rotation. Railway preliminary report.
LiteLLM, a widely used LLM proxy, disclosed that version v1.107.0, released 21 October 2026, was a compromised package. The project’s official incident post and a 23 October 2026 analysis by Microsoft Security describe credential theft through Python start-up hooks. Official sources: LiteLLM incident post; Microsoft Security Blog, 23 October 2026.
Those two events are different (a platform incident aimed at AI keys, and a compromised release of an AI-developer tool), but they point to the same operational lesson: AI tooling is now part of the software supply chain, and it needs its own review, key hygiene, and monitoring. We go further in AI-accelerated attacks and LLM supply chain risk, October 2026.
A note on language: a Nigerian financial-industry executive, interviewed by TechCabal on 13 November 2026, also used the phrase “Black October” for a separate early-October wave of attacks on Nigerian banks and a core-banking vendor. That is a different event set. TechCabal, 13 November 2026.
What Austin and Texas organizations should do next
You do not need a new slogan to act on a month like this. You need a short, specific list:
- Inventory and patch internet-facing PHP and self-managed GitLab, and any other software named in CISA KEV additions you actually run. If you do not have a current inventory, that is the first gap. Managed vulnerability management is the ongoing version of this work.
- Confirm endpoint and email coverage — especially help-desk reset procedures, MFA relay or fatigue risk, and EDR alerting — so a phished or vished account does not have a free path through the rest of the environment. Managed EDR.
- Treat AI tools as in-scope systems. If you run an LLM proxy, hold AI provider keys, or are building an agent, review how those credentials are stored, how packages are verified, and how the application can be abused. Vulnlogic offers an LLM App Assessment ($3,500), Agent Assessment ($6,500), AI Red Team ($9,500), and AI Guard ($1,500 / month). See AI / LLM security.
- Know your Texas notice clocks before you need them. Texas cybersecurity compliance.
- If you want a conservative first step, request the free external attack-surface snapshot. It covers publicly visible information only. It is not a penetration test.
Vulnlogic’s managed Core program is $3,000 per month for up to 100 users and includes vulnerability management, managed EDR, and email security. Plus is $5,000 and Complete is $7,000, the last of which includes a scoped annual penetration test. Details are on our Austin cybersecurity services page and on pricing.