Your EDR Is Glass and the Adversary Has a 4-Hour Clock — The Security Operating Model Needs Rebuilding
The capability threshold moved a step function this quarter
The defensive architecture most security programs are running on was invalidated this week, and the evidence arrived from independent directions at once. TrustedSec ran LLMs against five commercial EDR products and found all five share identical architectural patterns: YARA-style rules, behavioral logic, allowlists, prefilters, and local ML classifiers. Work that used to occupy a skilled reverse engineer for weeks now takes days. Anthropic's Mythos became the first model to clear both UK AISI simulated attack ranges, the benchmarks built specifically to test autonomous offensive cyber capability. OpenAI's GPT-5.5 cleared one of two. Both are outperforming an exponential trend line that was already doubling every few months.
Then the 4-hour exploitation window on PraisonAI: disclosure to active targeting in the time it takes to schedule a change-advisory meeting. An 18-year-old RCE in NGINX's rewrite module, present since 2007, surfaced alongside it, affecting nearly every modern web application.
The patch window used to be measured in months because attackers needed months. Now it is measured in months because procurement needs months; the attacker side moved while the defender side did not.
The AI infrastructure stack is under active exploitation
CISA added five AI tooling vulnerabilities to the Known Exploited Vulnerabilities catalog in a single week. LiteLLM (unauthenticated database queries), Ollama (GGUF model loader data exfiltration at CVSS 9.1), and OpenClaw (six simultaneous critical CVEs) are all being exploited in production. A Raspberry Pi honeypot dressed as an AI endpoint was indexed by Shodan in 3 hours and absorbed 113,000 requests in a month, with tooling that evolved mid-experiment to detect honeypots.
In the same window, Foxconn lost 8 terabytes of confidential designs from Apple, Intel, Google, and Nvidia to the Nitrogen ransomware group. The assumption that contract manufacturers held manageable supply-chain custody risk just proved aspirational.
The defender's response
Microsoft stood up MDASH (multi-model AI vulnerability discovery) and found 16 exploitable flaws in a single Patch Tuesday. Mozilla found 271 bugs in Firefox 150 using Claude Mythos with custom harnesses, against curl's 1 CVE from generic scanning. The variable is harness design, not model quality. The offensive application of these same capabilities by threat actors is a 12-18 month timeline, not a theoretical one.
Congress is routing Mythos access through NSA rather than CISA, which tells you which mission the government has prioritized. The private sector is on its own for the defensive application.
What this forces
A reasonable skeptic would point out that EDR vendors have weathered every prior architectural critique and shipped through it. The reasonable skeptic is correct about the past. What the skeptic does not explain is why a posture calibrated to an adversary that needed human researchers to chain exploits should hold against one that does not. The compensating controls, identity and network telemetry and behavioral analytics above the endpoint, are the ones that matter in the next eighteen months. The endpoint agent is no longer the load-bearing control.
What to do
Commission a red team exercise specifically targeting your EDR with AI-assisted reverse engineering tools within 30 days
Compress critical vulnerability patch SLAs from 30-day to 72-hour maximum for internet-facing assets by end of Q3
Audit all AI infrastructure tooling (LiteLLM, Ollama, model registries) for security controls by end of month — most were adopted without security review
Invest in custom AI vulnerability scanning harnesses for your 3 most critical codebases this quarter, following Mozilla's pattern