Chrome 101 Patches 41 Vulnerabilities, 6 Critical Memory Bugs
Key Takeaways Google has rolled out Chrome version 151, addressing 41 security vulnerabilities. The update includes fixes for six critical memory-safety flaws, primarily use-after-free bugs. These...
Key Takeaways
- Google has rolled out Chrome version 151, addressing 41 security vulnerabilities.
- The update includes fixes for six critical memory-safety flaws, primarily use-after-free bugs.
- These vulnerabilities could lead to browser crashes, memory corruption, or remote code execution.
- Users on Windows, macOS, and Linux are urged to update their Chrome browsers immediately.
Google has launched Chrome 151 to its Stable channel, delivering crucial security updates that patch 41 vulnerabilities. Among these are six critical memory-safety flaws that pose significant risks, potentially leading to browser instability, memory corruption, or the execution of malicious code.
Table Of Content
The updated versions are Chrome 151.0.7922.108/.109 for Windows and macOS users, while Linux users will receive version 151.0.7922.108. Google has indicated that the rollout will occur progressively over the coming days and weeks. Users are strongly advised to install the new version as soon as it becomes available to mitigate potential security risks.
A primary concern addressed in this update involves use-after-free vulnerabilities. These critical flaws manifest when a program attempts to access memory that has already been deallocated. Attackers can exploit such weaknesses by enticing users to visit specially crafted websites or interact with malicious web content, potentially compromising the browser.
Chrome 151 Vulnerabilities
Two critical use-after-free issues, identified as CVE-2026-19137 and CVE-2026-19170, impact WebGL, the technology integral to Chrome for rendering interactive 2D and 3D graphics on web pages. The former was reported anonymously, while the latter was discovered by a research team comprising Muhammad Alifa Ramdhan, Pan ZhenPeng, and Billy Jheng Bing Jhong from STAR Labs SG Pte. Ltd.
Additional critical vulnerabilities include CVE-2026-19149, another use-after-free bug found in Aura, Chrome’s core user interface framework. CVE-2026-19154 is a use-after-free vulnerability affecting the Skia graphics library, and CVE-2026-19172 points to a use-after-free flaw within Views, another component of Chrome’s interface.
Google also resolved CVE-2026-19157, an out-of-bounds write vulnerability within ANGLE, the graphics translation layer utilized by Chrome. Beyond these critical fixes, the update addresses 35 high-severity vulnerabilities spanning a wide array of browser components. These include the V8 JavaScript engine, GPU process, HTML renderer, media subsystem, Web Authentication implementation, extensions platform, payment features, translation service, workers, codecs, navigation handling, and crash-reporting functions.
Many of the high-severity issues are memory-related, encompassing heap buffer overflows, out-of-bounds writes, integer overflows, use of uninitialized memory, and further use-after-free vulnerabilities.
Critical Vulnerabilities Patched
| CVE | Affected Component |
|---|---|
| CVE-2026-19137 | WebGL (Use-after-free) |
| CVE-2026-19149 | Aura (Use-after-free) |
| CVE-2026-19154 | Skia (Use-after-free) |
| CVE-2026-19157 | ANGLE (Out-of-bounds write) |
| CVE-2026-19170 | WebGL (Use-after-free) |
| CVE-2026-19172 | Views (Use-after-free) |
These types of vulnerabilities are particularly concerning given that web browsers constantly process untrusted data from various sources, including websites, advertisements, downloaded files, scripts, and extensions, making them prime targets for exploitation.
Among the externally reported issues, Google recognized security researcher Sven Dysthe with a $5,000 bounty for reporting CVE-2026-19169, an insufficient validation flaw in Contextual Tasks. Other credited contributors include researchers from OpenAI Codex Security, Hap Security, QED Audit, and various independent contributors who reported vulnerabilities addressed in this release.
Google has withheld technical details and proof-of-concept information for these vulnerabilities. This standard practice aims to prevent attackers from exploiting unpatched systems by delaying the release of sensitive information until a majority of users have updated their Chrome browsers.
What You Should Do
- Update Immediately: Users should update their Chrome browser by navigating to the Chrome menu, selecting “Help,” and then “About Google Chrome.” The browser will automatically check for and install the latest version, prompting for a relaunch.
- Prioritize Organizational Rollouts: Organizations should expedite the deployment of Chrome 151 across all managed Windows, macOS, and Linux endpoints to minimize exposure to these high-impact browser vulnerabilities.
- Stay Informed: Regularly check for security updates for all software, especially web browsers, which are frequent targets for exploitation.
Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.



No Comment! Be the first one.