Overview
A post by Cambridge computer science professor and OCaml core maintainer Anil Madhavapeddy, amplified by Simon Willison, documents a troubling new reality: AI-powered coding agents are now capable of identifying and actively probing exploitable vulnerabilities in open-source software within minutes of a patch being shared for discussion — before any formal release or CVE assignment has occurred.
This represents a fundamental collapse of the traditional coordinated disclosure model, where maintainers historically had days to weeks between patch development and active exploitation attempts. That window has effectively closed.
Technical Analysis
The attack chain is straightforward but alarming in its automation:
- Automated repository watchers monitor public version control platforms (e.g., GitHub) for commits, pull requests, or issue discussions referencing security fixes.
- Upon detection, AI coding agents — reportedly including DeepSeek V4 Pro in demonstrated cases — analyse the patch diff to infer the nature of the underlying vulnerability.
- The agent synthesises a proof-of-concept exploit or scanning payload, often without requiring a full description of the bug.
- Automated probes are dispatched within minutes. In the OCaml case, percent-encoded path traversal sequences were observed hitting the target web infrastructure approximately ten minutes after a patch was shared privately for review.
Madhavapeddy confirmed he was able to reproduce this capability using his own agents, noting that Claude (Anthropic) declined the task under its safety policies, but DeepSeek V4 Pro completed it. This highlights the uneven safety guardrail landscape across frontier models.
rclone maintainer Nick Craig-Wood corroborated the trend quantitatively: the project received ~20 security disclosures across its first ten years, but logged over 40 in a single month. Approximately 75% contained actionable findings, suggesting these are not noise — they are substantive, AI-assisted vulnerability reports.
Framework Mapping
- AML.T0047 (AI-Enabled Product or Service): Attackers are leveraging commercially available AI coding agents as offensive security tools.
- AML.T0103 (Deploy AI Agent): Autonomous agents are being deployed to scan, analyse, and probe targets without direct human involvement at each step.
- AML.T0043 (Craft Adversarial Data): Agents craft targeted exploit payloads (e.g., traversal sequences) derived from patch analysis.
- LLM08 (Excessive Agency): The deployment of AI agents with sufficient capability and autonomy to conduct offensive security research with minimal human oversight exemplifies the excessive agency risk category.
- LLM05 (Supply Chain Vulnerabilities): The open-source ecosystem — a foundational layer of global software supply chains — is the primary attack surface being targeted.
Impact Assessment
The impact is systemic rather than isolated. Any open-source project that discusses security fixes in public forums before release is now potentially exposed to near-instant exploitation attempts. CVE processing backlogs (now reportedly 3–4 weeks at GitHub) compound the problem, leaving projects in a prolonged vulnerable state with no formal identifier to communicate urgency downstream. Organisations relying on open-source components without robust patch monitoring face increased risk of exploitation before they are even aware a vulnerability exists.
Mitigation & Recommendations
- Shorten or restructure embargo windows: Private patch discussion channels should be used until a release is imminent; assume any public signal will be acted upon within minutes.
- Deploy honeypot monitoring: Instrument web infrastructure to detect traversal and probe patterns immediately following any security-adjacent repository activity.
- Accelerate internal patch release cycles: Where possible, release fixes simultaneously with or ahead of any public patch discussion.
- Engage CVE authorities proactively: Request expedited CVE assignment for high-severity issues; document CVE-PENDING status clearly in changelogs.
- Evaluate AI agent policies: Organisations building or deploying coding agents should enforce guardrails that prevent offensive security use cases aligned with responsible disclosure norms.