Google has patched 47 security vulnerabilities in Chrome in the span of a week — and if you haven’t relaunched your browser, you’re still exposed. On Oct. 13, Chrome 155 moved to the Stable channel with 37 fixes (seven rated Critical); on Oct. 15, another update added 10 more (one Critical, six High). The builds — 155.0.8059.84/.85 for Windows and Mac, .84 for Linux — are rolling out gradually. Google reports no attacks in the wild, but the flaws are the kind that a single malicious web page can trigger.
The most urgent: CVE-2026-110922, a critical use-after-free bug in Chrome’s Prerender feature, and a buffer overflow in ANGLE, the layer Chrome uses to translate graphics calls. Six of the seven Critical bugs from Oct. 13 were use-after-free flaws in Browser, PDF, Network, Core, SVG and Media components. Notably, several were reported by Xinyang Ge of Anthropic — with one DOM memory-corruption flaw credited as “assisted by Claude,” highlighting AI’s growing role in vulnerability research.
Why memory bugs matter
Use-after-free — software accessing memory after it’s been released — dominates Chrome’s threat landscape. These bugs can crash a tab or, worse, let a malicious page run code. Three of the critical and high bugs sit in V8, Chrome’s JavaScript engine. Coming just six days after Chrome 155’s initial release (which fixed 247 vulnerabilities on Oct. 6), the pace proves browser maintenance is operating at breakneck speed.
What to do
Checking takes about a minute: open chrome://settings/help, let Chrome download the new build, and relaunch. Desktop builds should read 155.0.8059.84 or newer. Enterprise admins should verify endpoint compliance dashboards are green. With Chrome the world’s most-used browser, its bugs reach a huge audience — don’t be the one still running the vulnerable build.
The researcher angle deserves attention. Ge’s discoveries, some made with Claude’s assistance, underscore how AI is reshaping security research — finding flaws faster than humans alone. As browsers grow more complex, the cat-and-mouse game between researchers and attackers accelerates. For users, the defense is simple: keep auto-update on, and when Chrome asks you to relaunch, do it.
