Google has released a new Chrome 151 update that patches 41 vulnerabilities rated critical or high severity. Several of the fixed issues are tied to memory safety—a class of bugs that can destabilize software and, in worst cases, enable malicious code execution.
For users, the takeaway is straightforward: install the update as soon as possible. Even though the release notes reported no mention of active exploitation, unpatched flaws remain a common target for attackers.
What’s included in the Chrome 151 update
The latest browser refresh delivers fixes across multiple components and bug types. Google reported that six issues are critical, with the remaining 35 rated high severity.
In total, 24 of the 35 high-severity issues are also memory safety bugs. That means the update addresses a broad set of problems where incorrect memory handling can lead to serious outcomes.
The six critical-severity fixes
Google’s Chrome 151 release resolves five use-after-free vulnerabilities and one out-of-bounds write. The use-after-free flaws affect several graphics-related and rendering areas, including:
- WebGL
- Aura
- Skia
- Views
Beyond those use-after-free issues, the critical update also includes an out-of-bounds write in the ANGLE graphics engine. Together, these critical fixes show that memory handling remains a priority area in modern browser security.
How researchers contributed
Google indicated that external security researchers helped identify two WebGL security defects. However, it has not yet publicly confirmed the bounty rewards for those specific findings.
For the other critical weaknesses, Google attributed discovery to its internal teams. Separately, the company also recognized researchers for part of the high-severity set, while still limiting how much reward detail it disclosed.
In the broader list of 35 high-severity vulnerabilities, Google reported that 25 were discovered by Google and 10 credited to external researchers. Only two reward amounts were disclosed, and both were valued at $500.
What kinds of high-severity issues were patched
While memory safety bugs make up a large portion of the total, the Chrome 151 update also covers other classes of security weaknesses. Google described examples such as:
- Insufficient validations of untrusted input
- Inappropriate implementations
- Race conditions
- Integer overflows
These categories matter because they can undermine safety even when no memory corruption occurs. For instance, inadequate input validation can lead to unexpected behavior, while race conditions can create timing windows that attackers may attempt to exploit.
Why this update still matters, even if it’s not the biggest release
Google noted that this particular Chrome iteration does not contain as many fixes as some of the most recent browser updates. Still, the volume and severity of issues—especially the critical memory-safety bugs—make this release a meaningful security step.
Google also pointed to a faster patching pace, attributing improved speed to its use of AI-driven processes. Whether you care about the technology or simply the outcome, the result for end users is the same: more security problems addressed in a shorter time window.
Which versions are affected
The Chrome 151 update is rolling out in different builds depending on operating system:
- Windows and macOS: versions 151.0.7922.108 / 151.0.7922.109
- Linux: version 151.0.7922.108
If you use multiple devices, you may see rollout progress at different times. The safest approach is to update promptly once your browser indicates an available update.
Should you worry about active exploitation?
Google did not mention that any of the described vulnerabilities are being exploited in the wild. Even so, the absence of public exploitation reports is not the same as safety. Attackers often reverse engineer patched weaknesses and then look for similar unpatched targets.
That’s why security guidance remains consistent across browser releases: keep Chrome up to date, especially when the update includes critical severity issues.
Practical next steps for users
If you want to reduce risk, do the update as soon as possible. In general, Chrome installations will prompt you when updates are ready, and they typically apply after restart. After updating, take a moment to confirm that your browser reports the expected version.
Also consider encouraging colleagues or family members to update as well. Browser security is one of those areas where everyone benefits when everyone stays current.
Conclusion
The Chrome 151 critical bugs update patches 41 vulnerabilities overall, including six critical-severity memory safety flaws affecting components such as WebGL and the ANGLE graphics engine. With additional high-severity issues ranging from input validation weaknesses to race conditions and integer overflows, the update broadens protection across both rendering and broader browser logic.
Even without indications of active exploitation, the prudent move is to install the update now and keep your browser current going forward.
Source: https://www.securityweek.com/critical-vulnerabilities-patched-with-chrome-151-update/
