Google teste des mises à jour de Chrome deux fois par semaine face à l'explosion des failles découvertes par l'IA
La course à la sécurité logicielle impose désormais un déploiement continu. La correction d'un bug resté caché pendant 13 ans dans Chrome prouve l'efficacité de l'IA pour auditer le code legacy.
Pourquoi c'est important
L'automatisation de la recherche de vulnérabilités par l'IA réduit le délai entre l'apparition d'une faille et son exploitation, rendant obsolètes les cycles habituels de correctifs mensuels ou bimensuels.
Resume
L'utilisation de modèles IA de cybersécurité a permis à Google de corriger 1 072 vulnérabilités dans Chrome 149 et 150, surpassant le total des 23 versions précédentes. Craignant que des cyberattaquants n'utilisent les mêmes outils automatisés pour identifier des zéro-days, l'entreprise teste un déploiement de patchs deux fois par semaine en arrière-plan sans perturber la navigation.
Impact concret
Les RSSI et responsables informatiques doivent ajuster les règles de leur parc informatique pour autoriser l'application transparente de patchs bihebdomadaires sans interrompre les sessions de travail.
Applications concrètes
Audits automatisés de bases de code complexes par IA ; distribution continue de correctifs de navigateurs sans interruption de session ; colmatage rapide des failles d'isolation de sandbox.
Texte source original
With Chrome, Google pioneered the rapid release model for browser security. Now, Google says updates may need to change in the face of AI security analysis. According to the company, the number of bug fixes in Chrome releases has skyrocketed in recent months because AI is detecting so many flaws . We could be looking at more frequent updates soon, but Google is also working on ways to get those updates rolled out without bothering you as much. Google has released two major Chrome milestone builds recently—Chrome 149 in early June and Chrome 150 just a few weeks later. These two updates had a total of 1,072 bug fixes, which is more than the previous 23 releases combined. Such is the impact of giant cybersecurity AI models that can probe software for vulnerabilities at light speed. Some of these vulnerabilities were serious, too, with one bug hiding in the Chrome codebase for 13 years. If it had been exploited, an attacker could have bypassed the Chrome sandbox to make the browser access local files. Number of security bugs fixed in recent Chrome Stable release milestones. Credit: Google With the vastly higher rate of vulnerability identification, Google is worried bad actors will also be able to identify software flaws faster. Its goal is to ensure your Chrome install is always up to date or as close to it as possible. The first step toward that is the two-week update cycle the company announced earlier in 2026, but it's now piloting a system that would update Chrome twice per week . This would get patches out the door faster, ensuring that browsers are ready for the threat of AI-fueled attacks. Read full article Comments