Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

Type Confusion in Google Chrome V8

IdentifiersCVE-2025-10585CWE-843· Access of Resource Using…

CVE-2025-10585 is a high-severity type confusion vulnerability in Google Chrome's V8 JavaScript and WebAssembly engine. According to the provided content, Chrome versions prior to 140.0.7339.185 are affected. A remote attacker can trigger the flaw by convincing a user to visit a crafted HTML page, leading to heap corruption in the browser process. The issue was reported by Google Threat Analysis Group on 2025-09-16, and Google stated that exploitation exists in the wild at the time of disclosure.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause heap corruption in the Chrome browser process and may result in browser crashes or arbitrary code execution. The content also indicates the flaw was exploited as a zero-day in the wild and referenced in targeted espionage activity. As with other V8 memory corruption issues, further impact may depend on chaining with additional vulnerabilities to escape the sandbox or achieve broader system compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting use of untrusted websites and web content, especially high-risk browsing contexts likely to deliver crafted HTML/JavaScript. Use layered browser protections such as sandboxing, browser isolation, and network-based controls where available. However, the content does not describe any vendor-provided workaround, so patching is the primary mitigation.

Remediation

Patch, then assume compromise.

Update Google Chrome to version 140.0.7339.185 or later. The provided content states Google released Chrome Stable updates to 140.0.7339.185/.186 for Windows and Mac and 140.0.7339.185 for Linux to address this issue. Apply the vendor patch as soon as it is available in your channel, and ensure the browser is restarted so the update takes effect.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity160

Community discussion across Reddit, Mastodon, and other social sources.