Google Chrome 127.0.6533.73 Patches 10 Critical Vulnerabilities
Key Takeaways Google has released Chrome version 152, addressing 327 security issues and improvements. This update specifically patches 10 critical vulnerabilities across various Chrome components....
Key Takeaways
- Google has released Chrome version 152, addressing 327 security issues and improvements.
- This update specifically patches 10 critical vulnerabilities across various Chrome components.
- The most severe flaws are memory-safety issues, primarily use-after-free vulnerabilities.
- Users on Windows, macOS, and Linux are affected and should update their browsers immediately.
- While no active exploits are confirmed, the nature of these vulnerabilities poses significant risk.
Google has rolled out a significant security update for its Chrome browser, version 152, across Windows, macOS, and Linux platforms. This release, identified as 152.0.7977.64 for Linux and 152.0.7977.64/.65 for Windows and macOS, incorporates a total of 327 security enhancements and fixes. Crucially, the update remediates 10 vulnerabilities deemed critical, underscoring its importance for both individual users and corporate environments.
Table Of Content
The core of these critical flaws stems from memory-safety issues, with several prominent use-after-free vulnerabilities. These types of bugs manifest when a program attempts to access memory that has already been deallocated, potentially leading to severe security implications. Exploitation of such vulnerabilities could allow attackers to trigger browser crashes, gain unauthorized access to sensitive user data, or even execute arbitrary code within the compromised Chrome process.
Google has confirmed that the rollout of Chrome 152 will proceed incrementally over the coming days and weeks, ensuring broad availability to its user base.
Critical Vulnerabilities Addressed in Chrome 152
The 10 critical vulnerabilities patched in Chrome 152 span multiple integral components of the browser. These include critical issues within ANGLE, Aura, Chromecast, Views, Safe Browsing, and Mobile components.
Specific Critical Flaws
- CVE-2026-79282: This is a use-after-free vulnerability located in ANGLE, the graphics translation layer utilized by Chrome. Security researcher Goodluck was credited with reporting this flaw and received a $25,000 bounty.
- CVE-2026-79290 and CVE-2026-79052: Both are use-after-free vulnerabilities found within Aura, Chrome’s user interface framework.
- CVE-2026-79054 and CVE-2026-79224: These represent additional use-after-free issues, specifically impacting the Chromecast component.
- CVE-2026-79121: An improper input validation flaw also affecting Chromecast.
- CVE-2026-79150: A use-after-free vulnerability identified in Views.
- CVE-2026-78935: An uninitialized variable issue impacting the Mobile component.
- CVE-2026-79012: A use-after-free bug within the Safe Browsing feature.
- CVE-2026-79200: Another use-after-free vulnerability affecting Aura.
In addition to these critical patches, Chrome 152 incorporates numerous fixes for high-severity vulnerabilities across a wide array of subsystems, including WebGL, V8, WebRTC, Extensions, Autofill, GPU, Bluetooth, Sandbox, and Passwords. These high-severity issues encompass buffer overflows, out-of-bounds reads and writes, type-confusion errors, authorization flaws, race conditions, and information leaks.
Several high-severity fixes target ANGLE, addressing various issues such as out-of-bounds writes, buffer overflows, type confusion, use-after-free conditions, and uninitialized resources. Given ANGLE’s role in processing graphics, specially crafted malicious web pages or WebGL data could potentially exploit these vulnerabilities to compromise the browser’s code.
While Google has not indicated any active exploitation of these newly patched vulnerabilities, the company has temporarily restricted public access to detailed bug information and associated links. This measure is standard practice to allow the majority of users to update their browsers before exploit details become widely available. Restrictions may also persist if a vulnerability resides in a third-party library that has not yet been addressed in other dependent projects.
What You Should Do
- Update Immediately: Users should update their Google Chrome browser without delay. This can typically be done by opening the browser menu (three dots in the top-right corner), navigating to “Help,” then selecting “About Google Chrome.” The browser will automatically check for and download the update. A relaunch is required to complete the installation.
- Verify Enterprise Endpoints: Organizations should ensure that all managed Chrome installations update to version 152 through their established patch management systems and update channels.
- Stay Informed: Regularly check for security updates for all software, especially web browsers, which are primary targets for attackers.
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.