AI scanning can produce thousands of findings.
Anthropic's reported cost to build a working exploit for one long-hidden zero day 1
Mythos success rate on expert-level hacking challenges 2
Of breaches start with vulnerability exploitation 3
Days is the median time from vulnerability disclosure to known exploitation and it's getting faster 4
Running a pure AI scan multiple times a day on one hardened enterprise Java application costs about $200,000 per year in API fees before a single engineer reviews a finding.
At portfolio scale with multi-agent scanning, API costs can reach $2 million to $5 million per year.
Quarterly scans across 50 repos can produce hundreds of thousands of findings. At 30 minutes per finding, that becomes $6.4 million in engineering time.
The scanner ran. The security posture did not move.
Contrast Labs tested three AI scanners against the same codebase. Only 6% of findings were flagged by all three.
A control that returns different results on every run is not a control.
Know what is actually exploitable.
Block exploits before the patch ships.
Prioritize the issues that matter now.
When organizations learn about Mythos, the first reaction is often to run more AI scans. Naomi Buckwalter explains why that response creates more findings than protection, and why runtime evidence changes the security workflow.
Read the Mythos solution brief for the full breakdown of AI-built exploits, the cost of AI scanning at scale, and how Contrast combines AST and ADR to protect applications while teams fix what matters. Implementing a robust application security strategy requires defense based on evidence, not noisy findings
Download now
See which risks are actually reached, which attacks are active and where Contrast can protect you before the next patch ships.
It is real, but the bigger change is economic. Mythos did not invent exploitation. It made exploit development cheaper, faster, and easier to scale.
That matters because attackers do not need perfect automation. They need enough automation to find more weak points than your team can triage.
No. AI scanning is too expensive and inconsistent to run as your daily control.
Use AI scanning selectively for deep analysis on critical applications. Use deterministic testing and runtime protection for the security work that has to happen every day.
No. Scanning helps find possible issues. It does not protect the application while teams validate, prioritize and patch them.
Runtime defense closes that exposure window by observing active attacks and blocking exploits inside the running application.
Contrast does not ask AI to guess what matters from millions of lines of source code.
Contrast first observes the running application: code paths, data flows, HTTP requests, vulnerable execution, and attack behavior. Then AI can use that verified evidence to help generate targeted fixes.
Do not lead with backlog size. A big backlog does not tell the board whether the company can withstand an active attack.
Report on exposure windows, active exploit attempts, mean time to contain, and whether high-risk applications have runtime protection while fixes are underway.