Google Patches Actively Exploited Chrome 0-Day (CVE-2025-10585) — Update Now

By Ash K
Google Patches Actively Exploited Chrome 0-Day (CVE-2025-10585) — Update Now

What happened

Google has shipped an emergency update for Chrome to fix CVE-2025-10585, a high-severity type confusion flaw in the V8 JavaScript engine that is already being exploited in the wild. The issue was discovered by Google’s Threat Analysis Group and pushed to the Stable channel as part of an out-of-band security release.

Who is affected

All desktop Chrome users on Windows, macOS, and Linux are affected. The fixed builds are 140.0.7339.185/.186 for Windows and macOS and 140.0.7339.185 for Linux. Chromium-based browsers (e.g., Microsoft Edge, Brave, Opera, Vivaldi) typically follow with their own updates—administrators should monitor and patch those as soon as updates land.

Risk & impact

Type-confusion bugs in V8 can often be chained to achieve remote code execution via a malicious web page or ad frame. Because the vulnerability is under active exploitation, the practical risk is elevated until endpoints are patched and relaunched.

What to do now

  1. Update immediately: In Chrome, go to Menu → Help → About Google Chrome to trigger the update, then Relaunch.
  2. Verify the version: Ensure you’re on 140.0.7339.185/.186 (Windows/macOS) or .185 (Linux).
  3. Patch your fleet: For enterprises, enforce auto-update, schedule a forced relaunch, and watch for stragglers that have downloaded but not applied the new build.
  4. Harden your exposure: Temporarily reduce risky browsing on unpatched systems; consider tightening web content policies and ad/tracking controls until everything is current.

What else was fixed

This release also addresses several other high-severity issues (including use-after-free bugs in graphics and real-time comms stacks). Even if exploitation has only been confirmed for CVE-2025-10585 so far, apply the update to reduce overall attack surface.

Detection & monitoring tips

  • Look for chrome.exe spawning unusual child processes or script interpreters shortly before the update was applied.
  • Hunt for first-seen outbound destinations immediately following browser crashes or unexplained Chrome relaunches.
  • Correlate web proxy or DNS logs for users who reported tab crashes, sudden redirects, or scareware pop-ups.

Bottom line

Because exploitation is active, treat this as a patch-now event. Update Chrome across all desktops and keep an eye on Chromium-based alternatives as their vendors ship aligned fixes.

Ash K
Ash K
Ashton is a seasoned Cybersecurity Professional with over 25 years of experience in Cybersecurity Research, Cybersecurity Incident response, Products and Security Solutions architecture.