Google’s AI is digging up Chrome bugs that humans missed for years
Google has deployed an AI agent powered by its Gemini model to scan the Chrome browser’s codebase for vulnerabilities. The AI has already identified several long‑standing bugs, including a sandbox escape flaw that let the browser read local files. The sandbox escape bug had remained undetected for more than 13 years, highlighting the AI’s ability to find issues humans missed.
- ▪Google built an AI agent using its Gemini model to examine Chrome’s entire code for security flaws.
- ▪The AI discovered a sandbox escape vulnerability that allowed Chrome to read local files.
- ▪The sandbox escape bug had persisted unnoticed for over 13 years.
- ▪The AI’s findings demonstrate its effectiveness in catching bugs that human reviewers missed.
2 outlets in our directory ran this story, first to last over 1 hour. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Digital Trends files mainly under tech. We currently carry 563 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Digital Trends |
| Canonical URL | https://www.digitaltrends.com/computing/googles-ai-is-digging-up-chrome-bugs-that-humans-missed-for-years/ |
| Publication time | Thu, 30 Jul 2026 20:13:53 +0000 |
| Retrieval time | 2026-07-30T20:17:35.545Z |
| Last seen | 2026-07-30T20:17:35.545Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | WvqCPApq6xut · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
I’ve always assumed Chrome’s endless update notifications were just routine housekeeping with a batch of actually useful features every now and then. Turns out some of them are patching bugs that have been quietly sitting in the browser’s code for over a decade. So how exactly is AI catching these bugs? Google has built an AI agent powered by its in-house AI model, Gemini. Its entire purpose is to scan Chrome’s entire codebase for vulnerabilities, and it’s already proven itself. Google Chrome Among the other fixes, one catch stood out. It was a sandbox escape bug that let a compromised part of the browser trick Chrome into reading local files. The most interesting and frightening fact is that the flaw had survived undetected for more than 13 years.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Digital Trends.
Discussion
0 commentsMore from Digital Trends
