--- title: Google says AI helped Chrome fix 1,072 security bugs in... description: Google reports that AI-assisted tooling helped Chrome 149 and 150 fix 1,072 security bugs across two releases — more than the previous 23 milestones combined.... canonical: https://daily.dev/posts/google-says-ai-helped-chrome-fix-1-072-security-bugs-in-two-releases-6fajgqknw twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Google says AI helped Chrome fix 1,072 security bugs in two releases | daily.dev og:description: Google reports that AI-assisted tooling helped Chrome 149 and 150 fix 1,072 security bugs across two releases — more than the previous 23 milestones combined.... og:url: https://daily.dev/posts/google-says-ai-helped-chrome-fix-1-072-security-bugs-in-two-releases-6fajgqknw og:image: https://api.daily.dev/og/posts/6FAJgqkNw.png og:image:alt: Google says AI helped Chrome fix 1,072 security bugs in two releases og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Google says AI helped Chrome fix 1,072 security bugs in two releases **[BleepingComputer](https://daily.dev/sources/bleepingcomputer)** · 4 min read · 1 upvotes · 1 comments ## Summary Google reports that AI-assisted tooling helped Chrome 149 and 150 fix 1,072 security bugs across two releases — more than the previous 23 milestones combined. The company now uses LLMs throughout the entire vulnerability lifecycle: discovery, triage, severity rating, patch generation, and testing. Key systems include a Gemini-powered agent harness and Big Sleep (developed with DeepMind and Project Zero), which found a 13-year-old sandbox escape bug. Automated triage is saving hundreds of developer hours monthly, and in May alone the systems blocked over 20 vulnerabilities from reaching production. To close the patch gap between fix and delivery, Google is also moving to a two-week release cycle with weekly security updates, piloting twice-weekly security releases, and developing dynamic patching so Chrome can update without a browser restart. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How many security bugs did Chrome 149 and 150 fix using AI-assisted tooling? Chrome 149 and 150 together fixed 1,072 security bugs, more than the total fixed across the previous 23 Chrome milestones combined. Google now uses large language models throughout its vulnerability management process, including discovery, reproduction, severity assessment, developer assignment, patch generation, and test creation. This buildup followed earlier AI security projects like Naptime and Big Sleep. _Track how AI is reshaping browser security workflows like Chrome's on daily.dev._ ### What is Google's Big Sleep AI agent used for in Chrome security? Big Sleep is an AI-powered vulnerability discovery agent built by Google DeepMind and Project Zero that searches Chrome's codebase, including the V8 JavaScript engine and graphics components, for security flaws. It followed an earlier system called Naptime, which gave AI models specialized vulnerability research tools starting in 2023. _Developers evaluating AI vulnerability scanners can follow tools like Big Sleep on daily.dev._ ### How is Chrome changing its release cycle to reduce the patch gap for security fixes? Chrome is moving to a two-week major release cycle with weekly security updates, and Google is piloting two security releases per week to shrink the window attackers have to reverse-engineer disclosed vulnerabilities before users get patched. Google is also developing dynamic patching so updates can apply without restarting the browser, with Chrome 150 on macOS already able to auto-restart during inactivity. _Teams planning around faster Chrome release cadences can keep up with changes like this on daily.dev._ ## Community discussion Top comments from developers on daily.dev. **@kartiknvj** · 0 upvotes > The number that matters is that this beat the previous 23 milestones combined, which says AI is genuinely widening the top of the funnel for vulnerability discovery. The open question for me is the false-positive tax: if a model flags a thousand candidate bugs, someone still has to confirm each one is real and reachable before it counts. Does Google report how many AI-surfaced findings were actually valid, or only the ones that reached a fix? ## Similar posts on daily.dev - [An AI agent found 21 zero-days in FFmpeg for $1,000. Chrome just patched a record 429 bugs.](https://daily.dev/posts/an-ai-agent-found-21-zero-days-in-ffmpeg-for-1-000-chrome-just-patched-a-record-429-bugs--loichspdc) · The Next Web · 37 upvotes · 4 comments - [Firefox: The zero-days are numbered](https://daily.dev/posts/firefox-the-zero-days-are-numbered-swy2sidvw) · LWN.net · 1 upvotes · 1 comments --- Tags: [#llm](https://daily.dev/tags/llm), [#google-chrome](https://daily.dev/tags/google-chrome), [#ai-security](https://daily.dev/tags/ai-security) [View this post on daily.dev](https://daily.dev/posts/google-says-ai-helped-chrome-fix-1-072-security-bugs-in-two-releases-6fajgqknw) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Google says AI helped Chrome fix 1,072 security bugs in two releases","url":"https://daily.dev/posts/google-says-ai-helped-chrome-fix-1-072-security-bugs-in-two-releases-6fajgqknw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/google-says-ai-helped-chrome-fix-1-072-security-bugs-in-two-releases-6fajgqknw"},"datePublished":"2026-07-30T17:09:49.610Z","dateModified":"2026-09-14T07:16:40.715Z","description":"Google reports that AI-assisted tooling helped Chrome 149 and 150 fix 1,072 security bugs across two releases — more than the previous 23 milestones combined....","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b8fff3b60f8441d97fc1696e1a763aab?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b8fff3b60f8441d97fc1696e1a763aab?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"BleepingComputer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"BleepingComputer","logo":"https://media.daily.dev/image/upload/s--as8nJ3qy--/f_auto,q_auto/v1774959951/logos/bleepingcomputer?_a=BAMAMiWQ0","url":"https://daily.dev/sources/bleepingcomputer"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/google-says-ai-helped-chrome-fix-1-072-security-bugs-in-two-releases-6fajgqknw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"llm,google-chrome,ai-security","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"BleepingComputer","item":"https://daily.dev/sources/bleepingcomputer"},{"@type":"ListItem","position":3,"name":"Google says AI helped Chrome fix 1,072 security bugs in two releases"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/google-says-ai-helped-chrome-fix-1-072-security-bugs-in-two-releases-6fajgqknw","comment":[{"@type":"Comment","text":"The number that matters is that this beat the previous 23 milestones combined, which says AI is genuinely widening the top of the funnel for vulnerability discovery. The open question for me is the false-positive tax: if a model flags a thousand candidate bugs, someone still has to confirm each one is real and reachable before it counts. Does Google report how many AI-surfaced findings were actually valid, or only the ones that reached a fix?","datePublished":"2026-07-30T19:58:20.615Z","url":"https://daily.dev/posts/6FAJgqkNw#c-UDSGR2Uw2","author":{"@type":"Person","name":"kartik-nvjk","url":"https://daily.dev/kartiknvj","image":"https://media.daily.dev/image/upload/s--3gGgsVCw--/f_auto/v1781456774/avatars/avatar_TvTVeiMdkRCqWUDullFmy?_a=BAMAMiWQ0"}}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/google-says-ai-helped-chrome-fix-1-072-security-bugs-in-two-releases-6fajgqknw#faq","mainEntity":[{"@type":"Question","name":"How many security bugs did Chrome 149 and 150 fix using AI-assisted tooling?","acceptedAnswer":{"@type":"Answer","text":"Chrome 149 and 150 together fixed 1,072 security bugs, more than the total fixed across the previous 23 Chrome milestones combined. Google now uses large language models throughout its vulnerability management process, including discovery, reproduction, severity assessment, developer assignment, patch generation, and test creation. This buildup followed earlier AI security projects like Naptime and Big Sleep. Track how AI is reshaping browser security workflows like Chrome's on daily.dev."}},{"@type":"Question","name":"What is Google's Big Sleep AI agent used for in Chrome security?","acceptedAnswer":{"@type":"Answer","text":"Big Sleep is an AI-powered vulnerability discovery agent built by Google DeepMind and Project Zero that searches Chrome's codebase, including the V8 JavaScript engine and graphics components, for security flaws. It followed an earlier system called Naptime, which gave AI models specialized vulnerability research tools starting in 2023. Developers evaluating AI vulnerability scanners can follow tools like Big Sleep on daily.dev."}},{"@type":"Question","name":"How is Chrome changing its release cycle to reduce the patch gap for security fixes?","acceptedAnswer":{"@type":"Answer","text":"Chrome is moving to a two-week major release cycle with weekly security updates, and Google is piloting two security releases per week to shrink the window attackers have to reverse-engineer disclosed vulnerabilities before users get patched. Google is also developing dynamic patching so updates can apply without restarting the browser, with Chrome 150 on macOS already able to auto-restart during inactivity. Teams planning around faster Chrome release cadences can keep up with changes like this on daily.dev."}}]} ```