Google Chrome 153.0.8010.52 Fixes 16 Security Vulnerabilities Including Two Critical Flaws

What's being fixed

This release bundles 16 security fixes in total. Google has disclosed details for two of the most severe: CVE-2026-93374, a Critical-severity use-after-free vulnerability in Dawn (Chrome's WebGPU implementation), reported externally by Florian Schweitzer, and CVE-2026-93372, a Critical-severity buffer overflow in WebGL, reported internally by a Google researcher. As is standard practice, Google is withholding detailed bug information and links for the remaining fixes until most users have updated, and may continue to restrict access longer for issues that trace back to third-party libraries shared with other projects.

Why it matters for your stack

Dawn and WebGL are both graphics-rendering components that process content from web pages, meaning they can be reached simply by visiting a malicious or compromised site. A use-after-free or buffer overflow in these components can lead to browser crashes or, in a worst case, remote code execution. Because two of the fixed issues carry Google's highest severity rating, this update should be prioritized for any machine where Chrome is used to browse the open web, including shared workstations and systems running embedded Chromium-based browsers.

How to update

Chrome generally updates itself automatically; you can confirm you're on the patched build by opening Settings > About Chrome, which also triggers a check and restart prompt if an update is pending. The rollout is staged across Windows, Mac, and Linux and may take days to weeks to reach all users, so it's worth checking manually on critical systems rather than waiting for the automatic background update.