Google fixed 1,072 Chrome security bugs in two milestones, and published the harness

"In the last two milestones, Chrome 149 and 150, we have fixed 1072 security bugs, surpassing the total number of security bugs fixed across the prior 23 milestones combined." The post is unusually specific about the machinery. An agent harness built in early 2026 surfaced a sandbox escape that had "quietly survived in our codebase for more than 13 years," and has since gained a knowledge base of every prior Chrome CVE and the full Git history, developer-authored SECURITY.md files describing trust boundaries, a separate-context "critic" agent that consumes them, and the ability "to run vulnerability finding models over the codebase multiple times to account for model non-determinism." Fixing runs a candidate-generating agent, a critic that selects among the candidates, and test-writing agents, looping in imitation of code review. Guardrails are stated rather than implied: "Our AI analyzes source code strictly at rest, operating on locked-down machines that lack general internet access," with network requests intercepted against allowlists and subagents barred from files outside the source tree. The vulnerability reward program was restructured in March, after external reports for the year had already exceeded all of 2025, to focus researchers on submissions "additive to what we are finding internally". And Chrome is piloting two security releases per week.

Why it matters: Google's harness applies the same speed to defense that the intruder used against Hugging Face. The most reusable parts of this detailed production account are cheap: a machine-readable threat-model file in the repo, a critic in a separate context, and repeated runs because the model is not deterministic. Every figure is Google's own and unaudited.