Google has released a new security update for Chrome, addressing 15 security vulnerabilities, two of which are rated “critical.” Users of the browser should install the update to version 151.0.7922.169/.170 as soon as possible. Critical Chrome security vulnerabilities usually affect the core of the browser engine and, in the worst case, can be exploited remotely.
What’s behind the update?
On August 18, 2026, Google rolled out the stable version 151.0.7922.169/.170 for Windows and macOS, as well as 151.0.7922.169 for Linux. As usual, the update is rolled out in stages over several days to weeks, so if you don’t see it right away, there’s no need to worry. If you don’t want to wait, you can check for the update manually (instructions below).
In total, the update addresses 15 vulnerabilities: Google classifies two as critical and 13 others as high-severity. Among the affected components are the V8 JavaScript engine, the WebGL, Dawn, and ANGLE graphics libraries, as well as components such as CORS, USB, and the browser’s media section.
An Overview of the Critical Chrome Security Vulnerabilities
According to Google’s official release notes, the two critical vulnerabilities each involve buffer overflows in graphics processing. This is a classic type of memory error that, in the worst-case scenario, can be exploited to execute malicious code.
| CVE | Severity | Component | Vulnerability Type |
|---|---|---|---|
| CVE-2026-76034 | Critical | WebGL | Buffer Overflow |
| CVE-2026-76036 | Critical | Dawn | Buffer Overflow |
| CVE-2026-76038 | High | V8 | Type Confusion |
| CVE-2026-76047 | High | V8 | Type Confusion |
| CVE-2026-76043 | High | V8 | Incorrect Calculation |
| CVE-2026-76045 | High | WebGL | Use-after-free |
| CVE-2026-76040 | High | Browser | Use-after-free |
| CVE-2026-76046 | High | ANGLE | Buffer Overflow |
The remaining entries on the list include, among other things, a flawed CORS implementation, a race condition in the USB stack, an incorrect reference resolution in the core area, and an information leak in the Skia graphics library. Google detected most of the vulnerabilities internally using its own fuzzing tools, such as AddressSanitizer and libFuzzer. Two reports came from external security researchers, including a tip from OpenAI’s internal security department.
Is any of these vulnerabilities already being actively exploited?
No. Neither Google’s release notes nor reports from German tech media outlets such as Deskmodder currently indicate that active attacks are circulating. However, this does not change the recommendation to update as soon as possible: Once details about critical memory errors are made public, it’s usually only a matter of time before attackers develop suitable exploits.
How to Update Chrome
You can manually trigger the update to Chrome 151.0.7922.169/.170 in just a few steps if it hasn’t been installed automatically yet:
- Open Chrome and click the three dots in the top-right corner
- SelectSettings, then go to ” About Chrome ” on the left
- Chrome will automatically check for updates and install the new version
- Reload the browser by clicking the “Relaunch ” button to activate the update
Only the restart actually patches the vulnerabilities. Until then, the old, vulnerable version continues to run in the background.
Are Edge, Brave, and others also affected?
Since Microsoft Edge, Brave, Opera, and Vivaldi run on the same Chromium framework as Chrome, some of the patched vulnerabilities (particularly those in V8 and the graphics components) may also be present in those browsers. Experience shows that the vendors typically follow up with their own updates, usually with a delay of a few days. It’s therefore also worth manually checking the update settings for these browsers.
Conclusion
Two critical and 13 high-severity security vulnerabilities at once is an unusually large batch for a single Chrome update. Even though no active exploitation is currently known, this Chrome security vulnerability warrants an immediate update—the effort required is limited to a restart, while the risk of not updating is likely significantly higher.
Sources: Google Chrome Releases Blog
