Google has released another Chrome desktop security update. The September 17 Stable release moves Windows and macOS to 153.0.8010.52/.53 and Linux to 153.0.8010.52, with 16 security fixes including two Chromium-rated Critical vulnerabilities.
Current answer: Windows and macOS users on the general Chrome 153 Stable channel should verify that they are running 153.0.8010.52/.53 or a later build. Linux users should verify 153.0.8010.52 or later. If Chrome still shows .47/.48, that build included the September 15 fixes but is now behind Google’s September 17 security release.
Current Chrome desktop security versions
| Platform | September 17 Stable release | Reader action |
|---|---|---|
| Windows | 153.0.8010.52/.53 | Install the newest Stable update offered, relaunch if required and verify again. |
| macOS | 153.0.8010.52/.53 | Install the newest Stable update offered, relaunch if required and verify again. |
| Linux | 153.0.8010.52 | Update if the installed Chrome 153 build is still below .52 and verify afterward. |
Google says the release is rolling out over the coming days and weeks, so the exact build offered to an individual device can depend on rollout state.
What changed in Chrome 153.0.8010.52/.53?
Google’s September 17 Stable Channel Update for Desktop contains 16 security fixes.
The release identifies two Chromium-rated Critical vulnerabilities:
- CVE-2026-93374 — use after free in Dawn.
- CVE-2026-93372 — buffer overflow in WebGL.
The reviewed Google release does not state that either of these two newly listed Critical vulnerabilities is being exploited in the wild. Their Critical severity should therefore not be presented as confirmed active exploitation.
Should users on 153.0.8010.47/.48 update again?
Yes, when the newer Stable build is offered. Chrome 153.0.8010.47/.48 was Google’s September 15 Stable security release and included 42 security fixes. It remains a valid historical security update, but Google’s September 17 release is newer and adds another 16 security fixes.
A Chrome installation can therefore be protected against vulnerabilities fixed on September 15 while still missing fixes released two days later.
What about the older CVE-2026-87491 fix?
Google’s September 8 Chrome 153 Stable release fixed CVE-2026-87491 in 153.0.8010.36 for Linux and 153.0.8010.36/.37 for Windows and macOS. Google also confirmed that an exploit for CVE-2026-87491 exists in the wild.
That remediation history remains valid. However, .36/.37 is no longer an appropriate current security baseline because Google subsequently released .47/.48 on September 15 and .52/.53 on September 17.
The practical security question is therefore not only whether CVE-2026-87491 was patched, but whether Chrome is running the newest Stable security build available for the device.
What if Chrome shows version 154 on Windows?
Google began an Early Stable rollout of Chrome 154.0.8037.44/.45 to a small percentage of Windows users on September 16. A Windows installation already running that Early Stable build or a later legitimate Google-provided build should not be downgraded merely to match the Chrome 153 general Stable version listed here.
The 153.0.8010.52/.53 numbers are the September 17 general Stable release baseline. Users should let Chrome’s own update mechanism determine the newest release assigned to their device and channel.
How to check your Chrome version
Open Chrome’s About Chrome page and let the browser check for available updates.
For the general Chrome 153 Stable channel, Windows and macOS should move to .52/.53 and Linux to .52 or later.
If Chrome downloads a newer Stable build, allow the update process to complete.
A downloaded Chrome update normally needs a relaunch before the new browser executable becomes active.
Return to About Chrome after relaunch and confirm the newly installed version.
Does the September 17 update replace the September 15 update?
For current patch verification, yes: the September 17 Stable release is newer. The September 15 .47/.48 release remains part of Chrome’s patch history and fixed the vulnerabilities included in that release, but it is no longer the newest general Stable security state.
Users still on .47/.48 should therefore accept the newer .52/.53 or .52 build when Google offers it.
Are CVE-2026-93374 and CVE-2026-93372 actively exploited?
The reviewed September 17 Chrome release identifies both vulnerabilities as Critical but does not state that exploits for them exist in the wild.
That is different from CVE-2026-87491, for which Google explicitly disclosed that an exploit exists in the wild. Readers should not transfer the exploitation status of one Chrome vulnerability to other vulnerabilities simply because they appear in a later security release.
Does this Chrome version apply to Edge, Brave or other Chromium browsers?
No. Microsoft Edge, Brave and other Chromium-based browsers use their own release schedules and version numbers. Their users should follow the security and update guidance published by the relevant browser vendor rather than applying Chrome’s .52/.53 version number directly.
Why the update matters even if Chrome already patched CVE-2026-87491
CVE-2026-87491 created the original urgent version-verification task because Google confirmed active exploitation. Since then, Chrome has received multiple additional security updates.
That means a device can be protected against CVE-2026-87491 while still being behind on later security fixes. Maintaining the newest available Stable build is therefore more useful than checking only the historical minimum version for one CVE.
Current version timeline
| Date | Chrome desktop security state |
|---|---|
| September 8 | 153.0.8010.36 Linux and .36/.37 Windows/macOS; CVE-2026-87491 fixed and active exploitation disclosed. |
| September 15 | 153.0.8010.47 Linux and .47/.48 Windows/macOS; 42 additional security fixes. |
| September 17 | 153.0.8010.52 Linux and .52/.53 Windows/macOS; 16 additional security fixes including two Critical CVEs. |
Direct answer
For the general Chrome desktop Stable channel, Google’s September 17 security release is 153.0.8010.52/.53 on Windows and macOS and 153.0.8010.52 on Linux. It includes 16 security fixes, including Critical CVE-2026-93374 and CVE-2026-93372.
If Chrome still shows .47/.48 or an earlier Chrome 153 build, open About Chrome, install the newest Stable update offered for the device, relaunch and verify the installed version again. Windows users already legitimately receiving Chrome 154 through Google’s Early Stable rollout should follow the newer build offered by Chrome rather than downgrade.
Verification note
ThePulseSignal reviewed Google’s September 17 Stable Channel Update for Desktop, the September 15 Chrome Stable security release, the September 8 Chrome 153 release that fixed the actively exploited CVE-2026-87491, and Google’s September 16 Early Stable notice for the limited Windows Chrome 154 rollout. The latest general Chrome 153 Stable release is .52/.53 for Windows and macOS and .52 for Linux, with 16 security fixes including two Chromium-rated Critical vulnerabilities.