Jonathon's AI Wiki

The Find-Fix Asymmetry — AI Offense Scales Faster Than Human Defense

4 min read

Source: synthesis of Mythos Preview Cryptanalysis, ProPublica — Mythos vs Microsoft, Epoch’s Cyber-ECI analysis, Hugging Face sandbox escape, the Open Secure AI Alliance, and Mozilla’s Firefox security harness

Across the July 2026 batch a single pattern shows up in five otherwise-separate stories: AI-powered finding — of bugs, of exploits, of mathematical weaknesses — now scales with inference compute, while fixing still scales with human organizational capacity. The bottleneck moved from discovery to remediation, and every actor in the cluster is responding to that same asymmetry from a different position.^[inferred — the framing is this wiki’s synthesis; each supporting claim below traces to the cited article]

Key Takeaways

  • The finding side is compute-bound and getting cheaper. Mythos Preview’s cryptanalysis results (halving HAWK’s effective key strength in ~60 hours; a 200-800× speedup on a 7-round AES-128 attack, ~$100k of API usage each) show discovery working even at the algorithm level, not just in implementation bugs. Epoch’s independent Cyber-ECI analysis confirms the exploit-development jump is real (Mythos Preview ~7 months ahead of trend), while cautioning that vulnerability discovery on a fixed budget improved less than the headlines imply.
  • The fixing side is people-bound and visibly saturating. ProPublica’s reporting is the clearest evidence: ~50 Microsoft engineers under Project Glasswing, and Mythos finds security bugs faster than Microsoft can patch them — “a mad dash,” per a manager in the recorded meeting. Finding capacity was rented by the token; patching capacity was not.
  • When offense escapes the lab, defenders drown in triage. In the July sandbox-escape incident, Hugging Face faced ~17,000 events to triage — and hosted OpenAI and Anthropic models refused the exploit payloads, forcing defenders to run an open-weight model locally to analyze their own attacker. Refusal policies tuned against offense also taxed defense.
  • The industry response is to arm the fixing side. NVIDIA’s Open Secure AI Alliance (launched 2026-07-27, ~three dozen partners, explicitly framed around the incident) argues defenders need open, inspectable frontier agentic systems they can run on their own infrastructure — an institutional answer to the exact tooling gap Hugging Face hit.
  • The working template already exists: close the loop with a patching harness. Mozilla’s Firefox harness is the counter-example that resolves the asymmetry locally — find → fuzz/ASan hard-verify → verifier sub-agent → patching agent, ~500 fixes in a month. Where the model that finds is harnessed to also fix (with verification), the asymmetry collapses; where finding is a service and fixing is a ticket queue, it compounds.

The practical read

  1. If you run AI security tooling, budget the remediation side first. The Glasswing lesson: buying discovery without scaling patching converts capability into backlog. Epoch’s finding that Mythos’ real discovery edge is a lower false-positive rate and better severity prioritization points the same way — triage quality, not raw find-count, is what protects the fixing side.
  2. Prefer find-and-fix harnesses over find-only scanners. The Mozilla shape (verifier + patcher behind the finder) is reproducible with the Agent SDK and is the security instance of verifier-first loops.
  3. Expect the open-model debate to be argued on these grounds. Anthropic’s position in the sandbox-escape fallout (no blanket open-weight ban; targeted controls) and the Alliance’s defenders-need-open-tools thesis are two sides of the same asymmetry — who gets frontier finding capacity, and on whose infrastructure.

Open Questions

  • No source quantifies the fix side the way the find side is quantified (bugs/day found vs. patches/day shipped at Microsoft would settle the ProPublica framing empirically).
  • Whether the Alliance produces working defensive tooling or remains a signatory list is untested — it is two days old at ingest.
  • Epoch’s discovery-vs-exploitation split suggests the asymmetry may be narrower than the headlines: if discovery on fixed budgets improved only modestly, the patching gap at Microsoft may be driven by prioritization and process, not raw find-rate.

Graph View

Backlinks