Analysis

Black October: AI Made Old, Shelved Bugs Cheap to Prove

Black October's bug count was more noise than danger. The scary part: AI made exploits cheap to prove, so a PHP bug shelved for six years rooted firewalls.

MesmerTools•November 15, 2026•4 min

In October a viral tweet from Nick Dobos said "dozens if not thousands" of AI agent swarms were "hacking about half the internet right now". People were calling it Black October, after a month that included an emergency fix for PHP, which runs about 70% of websites.

So I pulled every bug filed in both Octobers, and the jump is more noise than danger. What changed is scarier: AI made exploits cheap to prove, and that's how a bug that sat on PHP's tracker for six years ended up rooting firewalls.

A large stopwatch on a dark background: on the left half an amber second hand streaks past with a long light trail, on the right a heavy grey hand has barely moved against a pile of unopened envelopes and tickets, beside the headline Proven fast. Fixed slow.

Was Black October worse, or just louder?

October brought 17,481 CVEs, the public IDs security bugs get, against 4,389 a year earlier.

CVEs published per month in the US National Vulnerability Database

Oct 2025
4,389
Nov 2025
3,116
Dec 2025
5,643
Jan 2026
5,143
Feb 2026
4,808
Mar 2026
6,304
Apr 2026
5,885
May 2026
6,985
Jun 2026
8,001
Jul 2026
9,919
Aug 2026
12,719
Sep 2026
15,074
Oct 2026
17,481
My count by publish date, as of November 2026: Dobos's viral claim that 3% of all "critical" bugs ever came in one month read a chart like this, which counts every CVE.

So I went through who filed them. Half the rise is vendors and projects publishing on their own code. Vendor CVEs usually arrive with patches, so that half is the fix queue moving.

Who filed October 2026's extra CVEs, compared with October 2025

Vendors, projects: own code
+6,380
ID issuers: others' bugs
+4,455
GitHub advisories
+1,265
Couldn't classify
+685
Microsoft has credited AI-assisted discovery since May, but the database doesn't record how a bug was found.

The US government also lists bugs known to be exploited, though that list lags. Here it is beside the filings at one grain per bug, and keep an eye on the two that light up.

The exploited list went from 31 to 36 while filings quadrupled, and the two amber grains are both IDs of one PHP bug.

So I wouldn't lose sleep over the count. The bug behind those grains had sat in plain view for six years.

PHP2Shell was found twice before AI proved it

PHP2Shell is the reason for that emergency fix, and it let strangers run code on a server. It was reported in 2020 and again around a 2024 audit, but every fix broke something and a stretched team couldn't choose.

Put those reports on a scale against the fixes and you can see what changed on August 11, when a security firm running an AI-assisted audit reported a way to run code.

The reports barely register against fixes that break things until one carries proof, and another firm working with models went from spotting the bug to running code on Drupal in a day.

I think "show me an exploit" worked as a filter because exploits were expensive. A model makes a specialist who already has a theory much faster, and an old report marked theoretical is a theory.

The fix took another 71 days, and while it was meant to be secret, two more groups reached the same root cause. My guess is that's the same cheapness at work.

The red spark is an exploit attempt logged four days before release, and it touches nothing because nobody knows where it came from.

The shelved bug ended up rooting firewalls

About 110 million PHP installs sit on versions past end of life, which sounds like forgotten blogs. But some of Palo Alto's firewall software runs PHP 8.0.30.

Two days after the fix, a suspected Chinese state actor chained the bug with a Linux kernel flaw and rooted exposed firewalls. It needed a management interface on the internet, which isn't the default. Researchers found Claude Code and an AI attack tool running Chinese models, but nobody says what the models did.

Here's the bug from audit to patch on one clock, zooming in until it lands inside one of those boxes.

Two dots in 1,560 had patched after 12 hours, and the same dead branch turned out to run inside a firewall.

So reread whatever you marked theoretical

If you run PHP, take the patched release, or on 8.1 or older check your distro for a backport. Keep the management interface of any box running PHP off the internet.

Then I'd go through your own tracker, because I can't tell you how many other backlogs hold a bug marked theoretical. That label was written when testing one was expensive, and in August it took a day.

More from the Blog