Schneier iconSchneierSep 10, 2026 ~8 min source read

AIs Compress Exploit Timeline

A brief rumor or high-level hint can be enough for AI agents to find and develop exploits faster than traditional open-source security workflows can respond, forcing changes to embargo, coordination, and mitigation practices.

Share this story

Send the public story page.

Useful takeaways from this story.

This pace of discovery undermines existing open source embargo practices and shortens the window between disclosure and active exploitation.

Practical responses proposed include private development, continuous shipping, defensive automation, and virtual patching via commercial CDNs.

# What happened A short, vague rumor about a security issue was enough for AI agents to locate and develop an exploit. The author reports that with only a rough idea of what the bug was about, his own agents found an exploit that could have been used before a public patch was available.

# Why this matters

# Evidence and community reaction

  • Anil, a Cambridge professor and OCaml maintainer, says the speed of AI-driven discovery appears incompatible with current embargo practices and that smaller maintainers lack access to frontier models. He reported using Claude and DeepSeek V4 Pro himself.
  • Simon Willison highlighted the broader conversation about how open-source communities must adapt.
  • Community comments noted automated watchers on repos and communications platforms, and reported exploit probes hitting targets minutes after a fix PR goes live.
  • An M-Trends reference in discussion claims the mean time to exploit has shifted to a negative value compared to older norms, indicating exploitation can precede or immediately follow disclosure.

# Concrete problems

  • Embargoes leak via signals: simply knowing that a private security discussion or embargo exists can act as a traffic analysis signal that tips off agents.
  • Unequal tooling access: "Mom and pop" maintainers often lack advanced generative models and defensive automation available to larger organizations.
  • Defensive speed mismatch: defenders must secure an entire attack surface, while attackers only need a single exploitable weakness and can use agents to find it fast.

# Proposed responses

  • Private development: reduce public exposure of high-level bug hints by shifting sensitive work into more private channels.
  • Defensive automation and autonomous testing: use automated pentesting, exploitability validation, and security control testing to shorten defenders' reaction time.
  • Virtual patching via commercial CDNs: apply mitigations at the edge while maintainers prepare and ship proper fixes.

# What to watch next

  • Whether open-source communities update embargo norms and coordination channels to reduce signal leakage.
  • Efforts to broaden access to defensive AI tooling for smaller maintainers.
  • Adoption rates of defensive automation and virtual patching services by projects with wide user bases.

# Bottom line Automated agents change the timeline: a rumor or hint can be enough for attackers to find exploits quickly. Open-source security workflows that depend on secrecy and human-paced responses will need operational changes to protect users.

More context around this story.

Loading more related stories...

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app