Google has distributed an urgent update for Chrome to correct CVE-2026-85046, a zero-day vulnerability in V8 that is being actively exploited. The solution requires updating to Chrome 152.0.7977.82 or higher and restarting the browser to apply the patch.
Google released the emergency update after detecting active exploitation of CVE-2026-85046, a high-severity zero-day in V8, the JavaScript and WebAssembly engine used by Chrome. The vulnerability enables a remote attacker to execute arbitrary code inside the browser sandbox when the victim visits a manipulated HTML page, a scenario typical in campaigns that combine malicious links, malvertising, or compromised websites.
The defect is classified as a type confusion in V8, a class of vulnerability that often provides dangerous primitives such as arbitrary read and write access within the JavaScript heap. Technical analysis points to the Maglev compiler and optimizations related to Array.prototype.sort, where certain inlining and specialization decisions can leave the engine in an inconsistent state that becomes exploitable.
Google has corrected the issue in the stable desktop channel with versions 152.0.7977.82 and 152.0.7977.83 for Windows and macOS, and 152.0.7977.82 for Linux. The update also addresses a total of twelve vulnerabilities, reinforcing the recommendation to apply the patch as soon as possible.
The company continues its policy of limiting technical details on selected flaws until the majority of users have updated, aiming to slow further exploitation. Researcher Salvatore Gulizia, known as Serotav, reported the vulnerability on 4 August 2026 and received a $1,000 reward. The published CVSS score is 8.8, reflecting the requirement for user interaction consistent with web-based attacks.
For users, the practical mitigation is straightforward: update Chrome and restart the browser so the patched version is running. In enterprise environments it is advisable to accelerate patch management, verify deployed versions, and prioritize high-exposure systems. Administrators should also monitor Chromium-based browsers such as Microsoft Edge, Brave, Opera, and Vivaldi, which will need to incorporate the fix in their own release cycles.
