Google Chrome 151 Update Fixes 7 Security Flaws Enabling Remote Code Execution and Sandbox Escape

Google has released Chrome version 151 to the Stable channel for desktop platforms, addressing seven security vulnerabilities.

Among these vulnerabilities is a critical use-after-free flaw, along with several high-severity issues affecting various components of the browser, including V8, DOM, Workers, networking, and Linux toolkit theming.

The update is being rolled out as version 151.0.7922.173/.174 for Windows and macOS, while Linux users will receive version 151.0.7922.173.

Google Chrome 151 Update Fixes 7 Security Flaws

The most severe issue, tracked as CVE-2026-76017, is a critical use-after-free vulnerability in Chromoting, which is Chrome’s remote desktop technology.

Use-after-free bugs occur when software continues to access memory after it has been released, potentially allowing an attacker to corrupt memory, execute arbitrary code, or crash the affected process.

In the context of web browsers, such flaws can play a significant role in exploit chains that could compromise a device after a user interacts with malicious content or a hostile remote-access mechanism. Google reported this issue internally on June 11, 2026.

Chrome version 151 also addresses CVE-2026-76018, a high-severity privilege escalation flaw in the Import component. Privilege escalation vulnerabilities are especially critical because they can allow code already executing with restricted permissions to gain broader access within the browser or the underlying operating environment.

While Google has not yet provided detailed technical information, the existence of a privilege issue alongside memory-safety vulnerabilities underscores the importance of prompt patching for enterprises that depend on Chrome’s sandboxing and process-isolation protections.

Several other high-severity bugs could potentially lead to remote code execution or facilitate browser sandbox escape attacks when combined with other vulnerabilities.

One such issue is CVE-2026-76020, a race condition in V8, Chrome’s JavaScript and WebAssembly engine. Race conditions in browser engines can sometimes be exploited to create unsafe memory states, making them appealing targets for attackers seeking to execute code via malicious websites.

Another issue, CVE-2026-76021, is a use-after-free vulnerability in the Document Object Model (DOM), which is a core browser subsystem that directly interacts with web content.

The update also resolves CVE-2026-76022, a buffer overflow in Chrome’s networking component. Buffer overflows remain a significant security concern because improper bounds handling can lead to memory corruption and, in some cases, arbitrary code execution.

Additionally, CVE-2026-76019 addresses incorrect authorization in Workers, Chrome’s background execution framework, while CVE-2026-76023 fixes improper resource control in Linux Toolkit Theming.

This latter issue was reported by Keita Sode and Daisuke Hatakeyama of SYZD Research and is particularly relevant for Linux desktop deployments.

Google has restricted access to technical details about the bugs and their associated issue links until most Chrome users have received the fixes.

This is a standard practice intended to reduce the risk that threat actors will quickly weaponize publicly available vulnerability information before patch adoption reaches a critical threshold.

Google has not indicated that any of the seven vulnerabilities are currently being exploited in the wild.

Organizations should prioritize deploying Chrome version 151 across managed Windows, macOS, and Linux endpoints, verify browser version compliance via endpoint management tools, and ensure automatic updates remain enabled on unmanaged devices.

Administrators should also monitor devices for outdated Chrome builds, as browser vulnerabilities often become components of phishing attempts, drive-by compromises, and multi-stage exploit campaigns.

Prevent incidents due to slow investigations. Power your Tier 1 with threat intelligence from 15K SOCs: Integrate TI Lookup in your SOC