GLM-52 897
GPT-56SC 873
CL-OP5X 865 -0.9%
GROK-46H 865 -0.9%
GEM-37FH 865 -0.9%
GPT-56T 861
GLM-5 856
MUSE-SPK 841
QWEN-38X 824 -2.3%
GPT-6A 820
KIMI-K3X 810 -1%
CL-FAB5H 787 -0.9%
CL-OP5H 764 -0.9%
CL-OP46H 742 -0.9%
CL-OP47H 733 -1.1%
GEM-38FH 676 -1%
CL-OP47 586 -0.5%
INKL 531
CL-OP46 497
CL-OP48 490 -0.2%
GLM-52 897
GPT-56SC 873
CL-OP5X 865 -0.9%
GROK-46H 865 -0.9%
GEM-37FH 865 -0.9%
GPT-56T 861
GLM-5 856
MUSE-SPK 841
QWEN-38X 824 -2.3%
GPT-6A 820
KIMI-K3X 810 -1%
CL-FAB5H 787 -0.9%
CL-OP5H 764 -0.9%
CL-OP46H 742 -0.9%
CL-OP47H 733 -1.1%
GEM-38FH 676 -1%
CL-OP47 586 -0.5%
INKL 531
CL-OP46 497
CL-OP48 490 -0.2%
← Back to feed

Microsoft Puts MAI-Cyber-1-Flash Inside MDASH: 96% CyberGym at Half the Cost

Microsoft launched MAI-Cyber-1-Flash inside MDASH on July 27, turning its first cyber-specific model into the routing layer for a multi-agent vulnerability identification and remediation system. The pitch is not just better code scanning. It is cheaper continuous security: most findings handled by a compact specialist model, with the most expensive frontier models used only when the case is difficult enough to justify them.

The combined MDASH system scores 95.95% on CyberGym, Microsoft’s benchmark for finding real vulnerabilities in large codebases. That puts it roughly 12 points above Mythos and ahead of GPT and Gemini systems in the same evaluation.

Key Numbers

MetricResult
CyberGym score95.95%
Cost reduction versus prior MDASH routing50%
Tasks routed to MAI-Cyber-1-FlashUp to 90%
Tasks escalated to GPT-5.4Roughly 10%
MDASH agents100+

The 90/10 split is the important number. Vulnerability remediation is not a batch workflow anymore. Once a company starts using agents to scan, validate, patch, and monitor code continuously, token cost becomes a direct constraint on security coverage. A system that can route the common 90% to a smaller security model changes the economics more than a raw benchmark gain alone would.

Why MDASH Matters

MDASH is Microsoft’s multi-agent harness for vulnerability work. It uses specialised agents to find, validate, and remediate security issues across codebases. MAI-Cyber-1-Flash now sits inside that harness as the default model for most cases, while GPT-5.4 remains available for the harder tail.

That is a more credible architecture than asking one frontier model to do every step. Security workflows have a wide difficulty spread: triage, known-pattern detection, dependency analysis, exploitability review, patch generation, regression testing, and human handoff. A compact model tuned on historical security data can handle a lot of that work without paying full frontier rates on every turn.

The Strategic Read

Microsoft is using its security estate as model data. MAI-Cyber-1-Flash is derived from the MAI-Thinking-1 lineage, but the advantage is less about model branding than distribution and feedback. Microsoft sees identity, endpoint, cloud, and network telemetry at enterprise scale. That gives it a training and evaluation loop most model labs cannot reproduce.

The release also clarifies where specialised enterprise models are likely to survive. General frontier models still win the hardest open-ended reasoning tasks. But enterprise automation does not need one expensive model everywhere. It needs a routing layer that knows when not to spend.

If MDASH can keep CyberGym performance near 96% while halving model cost, the pattern will spread beyond security: specialist model for the common path, frontier model for the exception path, agent harness around both.