Blog

A golden age of cybersecurity?

Toby White · November 2026

Black October1 is being followed by an even Blacker November. I don’t know if this is Russians, Iranians, bored teenagers, or autonomous AI swarms that broke out of confinement, but it sort of doesn’t matter. We’ve passed some sort of threshold where 40 years of insecure practices are going to catch up with all of us.

I go back and forth on what I think this means long term. I mean it’s clear in the short term we are going to be in for a rough ride. Those 40 years of insecurity are not going to be cleared up quickly.

It’s quite something to see that all of our carefully constructed “responsible disclosure” practices are being torn up2 — and rightly so. When vulnerabilities were rare, it made sense to slow down a bit, coordinate disclosures across vendors and make sure we can get the mitigations out effectively, without alerting any bad guys to a new zero-day.

These days you have to assume that if any single person has found a vulnerability with AI, then very soon, so will anybody else interested in the same topic.3 If you try and coordinate disclosure, you’re just slowing down defenders while the attackers go full blast at every new vulnerability.4

If that’s the long-term status, that’s a really hard world for us all to live in. The frontier labs have noticed the problem. OpenAI in particular is devoting “a significant amount of [their] frontier compute”5 to this problem — the trouble is, it’s all shutting the stable door after the horse has bolted. Last week they found nearly 1000 previously unreported Linux kernel vulnerabilities and found fixes for them.6 Which, you know, great — but those are 1000 vulnerabilities which are already out there and deployed. This is the problem we already had, they’ve just shown it to us.

There is a way to view this positively. We could quite reasonably now ask OpenAI et al to go across every common piece of software that exists, audit for vulnerabilities and fix them. In fact, someone will do this whether or not we ask them to. And, we can demand of our LLMs that every new piece of software written is free of vulnerabilities. That’s a quite reasonable expectation as well; it’s hard to prove a negative, but these days it’s actually quite hard to get Claude to output code containing vulnerabilities.

Maybe if that happens, and then we wait a year or two for install cycles, then by 2030 we could be looking at a future world completely free of software vulnerabilities. I’ve spoken to a couple of very senior cybersecurity researchers who believe this wholeheartedly. They’re going to batten down the hatches for the next couple of years, in the expectation that a golden age of computer security will dawn within the next decade.7

I don’t think I agree. Or rather, yes, I could probably buy into the idea that 5 years from now, nobody is writing software with vulnerabilities like we see today. But:

  • lots of attacks come not from logic vulnerabilities but eg architectures pushed outside of their design space, or multiple system architectures interacting and subtly breaking each other’s assumptions. You could place the entire domain of prompt injection under this header.8
  • hardware attacks are much harder to deal with and replace. Rowhammer, RowPress, StackWarp, etc9 stem from quite basic hardware architecture issues, and even if starting now we could design chips without any such vulnerabilities, it’s a much longer turnover cycle till we replace all the hardware out there.

But worse; ultimately all our systems work in the real world, and physics doesn’t respect our security boundaries. You can sniff CPU activity by listening to the sounds of a CPU fan even today.10 What could an AI do in 10 years’ time, equipped with a broad range of sensors? On this view, if the AI can perform arbitrarily complex physical interrogations of a system, ultimately there is no defence.

This is a restatement of the AI doomers’ viewpoint from a pure cybersecurity perspective — once AI is loose in the world, certain battles are already lost.

I’m not sure I believe that either though. I see two competing exponential growth curves here; one for the attacker, one for the defender. Which dominates long-term? The only honest answer is “I don’t know”. I’m very mistrustful of the “golden age of security” view; I think that involves radically underestimating the breadth of the risk landscape. I maybe object a bit less to the doomer view which at least shows more imagination.

But I think both sides of the argument underestimate the incentives involved and the power of negative feedback loops. Cybersecurity was already an arms race; I think AI massively accelerates the arms race on both sides, but wherever defenders or attackers gain an advantage, there will be resources and capital thrown at the other side, and very often, that means that you end up with some dynamic equilibrium balancing out.

I do think the advantage lies with the attackers for the next few years;11 I do think that in today’s sense “software cybersecurity” will be solved on the same timescale. There’s an enormous amount of work to be done in securing our existing systems, and there will be a lot of money lost to criminals12 as we play catch-up. We will win this software security battle in the end. But the war is just going to migrate to different battlefields; we will have to keep on fighting.

Sources

  1. Fortune, 29 Oct 2026; Axios, 28 Oct 2026 ↩︎
  2. Bitcoin Core drops embargoes for LLM-findable bugs, CoinDesk 23 Oct 2026; QEMU shortening embargoes, InfoQ 3 Oct 2026; oss-security thread “Coordinated Disclosure in the LLM Age”; Schneier and Hathaway, 1 Jun 2026 ↩︎
  3. OpenAI, “A thousand fewer paths to root”, 4 Nov 2026 — about 400 of the 948 were patched or publicly discussed by other contributors within ten days of the scan ↩︎
  4. PHP2Shell timeline, TechTarget; the early-disclosure debate; Exploitarium, 30+ zero-day exploits published with no notice to maintainers, Infosecurity Magazine 2 Jul 2026; Josh Bressers, “Dear Open Source Developers: It’s OK not to embargo”, 27 Oct 2026; Hacker News, 28 Jun 2026, slow disclosure cannot keep up with AI-found bugs, so publish; Hacker News, 23 Oct 2026, the PHP2Shell leak let a team shut services down before the fix ↩︎
  5. Eric Wallace of OpenAI, quoted by TechCrunch, 5 Nov 2026 ↩︎
  6. OpenAI, 4 Nov 2026; BleepingComputer, 6 Nov 2026 ↩︎
  7. Public versions of the view: the closing section of OpenAI’s post above; Schneier in the Guardian, 8 May 2026 ↩︎
  8. Ten prompt-injection payloads found planted in live web pages, Forcepoint via Infosecurity Magazine 23 Apr 2026; EchoLeak, a zero-click data leak from Microsoft 365 Copilot, BleepingComputer 11 Jun 2025 ↩︎
  9. RowPress (2023); StackWarp (AMD Zen, Jan 2026) ↩︎
  10. Fan noise reveals CPU load, Islam et al. 2018; ECDSA key recovered by filming a device’s power LED, Nassi et al. 2023; AI model structure read off a GPU through a wall with an antenna, KAIST ModelSpy, NDSS 2026 ↩︎
  11. sshole (CVE-2026-123158) exploited within nine hours of the patch, Help Net Security 6 Nov 2026 ↩︎
  12. Binance theft, $6.4bn, 29 Oct 2026, Elliptic ↩︎