← Back to blog
October 31, 2026

When the AI Starts Writing the Zero-Days

We have officially reached the point where the AI isn't just helping you write cleaner CSS; it's actively figuring out how to break into your servers before the major distros have even had a chance to compile a fix.

A recent report highlights a serious use-after-free vulnerability in the Linux kernel’s IPv4 TCP stack, specifically targeting systems utilizing Multipath TCP (MPTCP). While kernel bugs are a dime a dozen, the kicker here is that an unreleased research model from Anthropic’s Frontier Red Team successfully weaponized the flaw. According to a report by WebHosting Today, the AI managed to chain together a remote root exploit that triggers during the standard TCP handshake. As of this moment, major players like RHEL, AlmaLinux, and Ubuntu are still scrambling to push out stable, patched kernels to their repositories.

The Speed of the Adversary

In the two decades I have spent in web hosting, the rhythm of security has usually followed a predictable pattern: a researcher finds a bug, a patch is developed, the patch is disclosed, and then the exploit scripts start showing up on forums a few days or weeks later. That window is our breathing room. What we are seeing now is the total collapse of that timeline. If an LLM can analyze a kernel commit and produce a working root shell in a fraction of the time it takes a human team, the defensive advantage of "security through obscurity" or even "security through slow disclosure" is dead.

For hosting providers, this is a logistics nightmare. We are managing thousands of nodes, and the expectation of 99.9% uptime doesn't play well with the need to emergency-reboot every hypervisor because an AI found a way to bypass the TCP handshake. If your infrastructure relies on MPTCP, you are currently sitting on a live wire until those upstream packages land. It’s a stark reminder that our reliance on stable, slow-moving distributions is a double-edged sword when the attackers are moving at the speed of compute.

I suppose we should be grateful the AI was polite enough to tell the Red Team what it found before it started scanning the entire IPv4 range on its own accord.

The Bottom Line

This isn't just another CVE to add to the pile; it’s a shift in the landscape. We are entering an era where the time-to-exploit is effectively zero. If you haven't automated your kernel patching and reboot cycles yet, you're no longer just behind the curve—you're the target.