Patch Now: Chrome Flaw Under Active Attack, Google Confirms

Chrome just became the latest battlefield in an ongoing war over memory safety.

Google has pushed an urgent security update after uncovering multiple high-severity vulnerabilities — one of which is already being exploited in the wild. In a rare and pointed advisory, the company confirmed: “We are aware that an exploit for CVE-2026-5281 exists in the wild.”

That single line shifts this from routine patching to active threat response, where attackers aren’t waiting—they’re already moving.

Inside CVE-2026-5281

The vulnerability, tracked as CVE-2026-5281, is a use-after-free flaw affecting Chrome’s WebGPU implementation through its Dawn GPU abstraction layer.

This class of vulnerability occurs when a program continues to access memory after it has been freed, creating an opportunity for attackers to manipulate memory and execute malicious code.

In this case, the issue lies in Dawn — a cross-platform component that enables WebGPU and interacts closely with the underlying system hardware, increasing the potential impact of exploitation.

Google has confirmed that CVE-2026-5281 is being actively exploited in the wild. Attackers can exploit this flaw by triggering memory mismanagement within the GPU processing pipeline. This can lead to memory corruption, allowing adversaries to execute arbitrary code within the browser context.

In more advanced attack chains, the vulnerability could be combined with additional flaws to bypass Chrome’s sandbox protections and gain deeper access to the underlying system — potentially resulting in full device compromise.

The Chrome patch release addressed 21 vulnerabilities, many involving memory-safety issues such as use-after-free and heap buffer overflows across components, including WebGL, WebCodecs, CSS, and the V8 JavaScript engine.

The vulnerabilities that were patched impact Chrome versions prior to 146.0.7680.177 on Linux and 146.0.7680.177/178 on Windows and macOS.

Reducing risk from browser-based attacks

Given the active exploitation of this vulnerability, organizations should prioritize reducing exposure and layering defensive controls.

• Apply the latest patch and verify deployment across all managed systems using endpoint management tools.
• Monitor endpoint and network telemetry for signs of exploitation, including unusual browser crashes, anomalous GPU activity, or suspicious outbound connections.
• Restrict high-risk browser features such as WebGPU, WebGL, WebAssembly, and limit extensions through enterprise policies.
• Strengthen endpoint protections by enabling EDR/XDR behavioral detection, exploit mitigation controls, and application allowlisting.
• Reduce the attack surface through least-privilege access, network segmentation, and DNS or web filtering to block malicious infrastructure.
• Test incident response plans and use attack-simulation tools for browser-exploitation scenarios.

This incident highlights a broader trend: modern browsers continue to grow more complex, incorporating features like GPU acceleration and real-time rendering that expand the attack surface. Memory safety vulnerabilities — particularly use-after-free issues — remain an ongoing challenge.

At the same time, advances in AI are contributing to faster vulnerability discovery and potentially shorter timelines between disclosure and exploitation.

Editor’s note: This article originally appeared on our sister publication, eSecurityPlanet.