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.
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.

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
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
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.
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.
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 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.
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
NVIDIA MotionBricks: The 15,000 fps Isn't the News
MotionBricks' 15,000 fps is mostly a counting choice. I ran it on a laptop. The news is fast, smooth and accurate at once, enough to replace game transitions.
ChatGPT Images 2.6 GIFs Act Like Sprite Sheets: They Keep the Look, Lose Count
ChatGPT Images 2.6 GIFs behave like one sprite sheet cut into frames, so they keep the look and lose count. In 18 juggler runs, none kept three balls.