Chrome 153 critical security update: install 153.0.8010.52/.53 now

If you use Google Chrome on a home PC or Mac, update it today. This is a mid-cycle Chrome 153 security bump, not the big September 8 Stable promotion we already covered.

On Thursday, September 17, 2026, Google’s Stable Channel Update for Desktop moved Stable to 153.0.8010.52/.53 for Windows and Mac, with 153.0.8010.52 for Linux, rolling out over the coming days and weeks. The same note counts 16 security fixes. Two of them are rated Critical. Secondary coverage such as PiunikaWeb is useful for the plain-language summary. For versions and CVE wording, prefer Google’s Stable post.

This article is separate from our earlier Chrome 153 Stable promotion note (the September 8 train with the huge security list) and from the CVE-2026-85046 Chrome 152 patch-now story. Same habit every time: update, fully quit, relaunch, prove it with chrome://version.

Why this one is worth interrupting your tabs

Critical graphics bugs are the kind of issue that can matter on ordinary browsing. Google’s Stable note names:

CVE-2026-93374 (Critical): Use after free in Dawn (WebGPU stack). Reported by Florian Schweitzer.
CVE-2026-93372 (Critical): Buffer overflow in WebGL. Reported by Google.

Memory bugs in low-level graphics paths are the ones you do not casually leave open. A crafted page or web app that hits WebGPU / WebGL the wrong way is exactly the class of risk browser vendors rush to close. Google is still restricting some bug details until more users are patched, which is normal and not a reason to wait.

The release also includes several High issues (examples from the same Stable note: Tracing, PDFium, Skia, Extensions, ORB, V8) plus Medium and Low items. You do not need to memorize the list. You need the new build running.

Target builds

From Google’s September 17 Stable Channel Update:

Windows / Mac: 153.0.8010.52 or 153.0.8010.53
Linux: 153.0.8010.52

If chrome://version still shows an older 153.0.8010.x from earlier in the week (for example the September 8 .36/.37 train), you are behind this security package. Get to .52 or .53.

How to update and verify

Open Google Chrome on the computer you actually browse on.
Check for updates:
- Windows / Linux: Menu (three dots) → Help → About Google Chrome.
- Mac: Chrome menu → About Google Chrome.
Stay on that page until the download finishes and Chrome offers a relaunch, or until it already shows 153.0.8010.52 or .53.
Relaunch when prompted. Do not click Later and leave old windows open.
If the version still looks old, fully quit Chrome (every window). On Windows, confirm no leftover chrome.exe processes in Task Manager. On Mac, use Chrome → Quit Google Chrome. Then open Chrome again.
Type chrome://version in the address bar and read the first version line. You want 153.0.8010.52 or 153.0.8010.53 (Linux: .52).
Repeat on other computers you use, including a laptop that stays open for days and any shared family PC that still runs Chrome.

Chrome can download an update quietly while you keep reading on the old process. Downloaded is not the same as running. The address-bar check is the proof.

Do this / don’t do that

Force About Google Chrome, relaunch, and confirm chrome://version shows 153.0.8010.52 or .53.
Update each Chromium browser you actually use (Edge, Brave, and so on) on its own schedule. Updating Chrome does not update them.
Give Stable a day to reach you if About Chrome says an update is coming but does not offer .52/.53 yet, then check again.

Don’t

Do not assume a Windows reboot alone applied this build if chrome://version is still behind.
Do not leave old Chrome windows or background helpers running after an update prompt.
Do not skip the version check because the About page looked green.
Do not confuse this mid-cycle security package with “I already moved to Chrome 153 last week, so I am done.” Last week’s major train is not this week’s Critical graphics fixes.

A note on automatic updates

Chrome is good at downloading updates in the background. Keep that on. After a Stable note with two Critical fixes, take the extra minute anyway: force the check, fully quit, relaunch, read chrome://version. Then go back to your tabs.

Phone Chrome follows store or package updates. This Stable Channel note is for the desktop browser on your desk or lap.

Bottom line

Google’s September 17, 2026 Stable update ships Chrome 153.0.8010.52/.53 (Linux .52) with 16 security fixes, including Critical Dawn / WebGPU and WebGL bugs (official Stable Channel Update). Update Chrome on your own computer, fully quit and relaunch so the new process runs, and confirm chrome://version. That is the whole job.

Image: Google Chrome marketing homepage art.