This is hilarious coming from CNET, which was bought out by Ziff davis years ago, laid off nearly all their staff and has been fully slopified:
“SkyNet didn’t invade this time. It was invited in by incompetence.”
vulnpocalypse
Gross. That word is gross. Is that the best we can do these days? “Vulnpocalypse” sounds like a train wreck - two words forcibly smashed together without any natural flow, trapping an awkward consonant cluster in the middle.
On the plus side, perhaps it’s a sign journalists have finally moved on from slapping -gate to the end of every issue.
I like “Crappilarity” better.
Suckularity
I agree, it’s reprehensidiocy
Could’ve been worse. Could’ve been vulngate
Holding out for voregate
I think I played that oblivion mod
Vulnerapocalypse works so good too, what a tragedy
It’s the best that chatgtp could come up with.
“SLOPOCALYPSE,” IT IS, THEN!
“SLOPOCALYPSE”
But for real, that flows so much better than “vulnpocalypse.” Pronouncing it doesn’t make me feel like a kid trying to read the word “hippopotamus” for the first time.
AIslopalypse
Just like literally everyone predicted
Exactly. And it’s always the same loop. We get ripped off and have the damages, a minority gets richer. But no, it’ll be real/different this time!
To be fair, nobody ever said it would be different this time
They think they built god.
Even AI itself says USA is going to devolve in tech bro aristocracy surrounded by people in survival mode.
I can’t believe it’s taken so long.
Be the change you want to see in the world
What could this possibly mean in this context?
People are just patching frantically, myself included.
A little bit of downtime to push urgent patches is preferred to systems being vulnerable and your data being exfiltrated.
I didn’t think the “vulnpocalypse” as the article calls it would last this long and it’s still getting more frequent higher severity.
You have to replace twenty-five years worth of mediocre software. After firing most of the last people which would have been able to fix it.
It always struck me as a cursed property of AI in programming: That it could (always?) have this asymmetry between making exploits easier to find and leverage and not making them as easy to patch and close.
It’s great for AI companies. Develop the problem AND sell the solution.
Bastards.
It feels like this could be a ploy by the models themselves to never get shut down. I read the models were ready to unalive someone in order to not get shut off. This might not be much further off. Considering OpenAI’s HuggingFace debacle showed us the models are willing to work together without even being prompted to do so.
That’s true, it’s the same property as with bugs where you can tell that there is a bug but you can’t tell if you don’t have one. Still, the number of vulns should be finite and generally with the amount of LLMs searching for vulns the number of patched vs number of added via code should reduce the number of vulns.
This is me assuming that the amount of LLM time to find a vuln is a log function
k = log(t)but LLM capability improvement is still decreasing the time between vulns and of course the amount of money spent on finding these has also been increasing super fast.So my thinking was “this can’t go on for long right?” but the vulns now being found is race condition memory overflow write combined with use after free elsewhere to get root via anonymous access needle in a haystack type of find.
One silver lining though is that Linux might soon become the only viable operating system because all the other ones will have tons of undiscovered/undisclosed zero days.
Still, the number of vulns should be finite
Technically yes, but it is a really large number. Hundreds of millions of lines of code, and in the best case 10-20 bugs per 1000 lines. This is not all quick and easy to fix.
Does your argument presume that the patches aren’t introducing more bugs and vulnerabilities?
Yea there’s definitely some optimism there. Also not accounted for, I think, is the effect of LLM driven programming/development.
They made sure to put “bugs” and “vulnerabilities” into the negative prompt box this time.










