CVE-2025-10891

8.8 HIGH

📋 TL;DR

An integer overflow vulnerability in Chrome's V8 JavaScript engine allows remote attackers to trigger heap corruption via malicious HTML pages. This affects all users running vulnerable versions of Google Chrome, potentially leading to arbitrary code execution. The vulnerability is remotely exploitable without user interaction beyond visiting a malicious website.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: All versions prior to 140.0.7339.207
Operating Systems: Windows, macOS, Linux, ChromeOS
Default Config Vulnerable: ⚠️ Yes
Notes: All standard Chrome installations are vulnerable. Extensions or security settings do not mitigate this vulnerability.

📦 What is this software?

Chrome by Google

Google Chrome is the world's most popular web browser, used by over 3 billion users globally across Windows, macOS, Linux, Android, and iOS platforms. As a Chromium-based browser developed by Google, Chrome dominates the browser market with approximately 65% market share, making it a critical compon...

Learn more about Chrome →

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full remote code execution with the privileges of the Chrome process, potentially leading to system compromise, data theft, or ransomware deployment.

🟠

Likely Case

Browser crash (denial of service) or limited code execution within Chrome's sandbox, potentially enabling data exfiltration or further exploitation.

🟢

If Mitigated

No impact if Chrome is fully patched or if exploit attempts are blocked by network/web security controls.

🌐 Internet-Facing: HIGH - Attackers can host malicious HTML pages on websites, making all internet-facing Chrome instances vulnerable.
🏢 Internal Only: MEDIUM - Internal users could be targeted via phishing emails or compromised internal websites, but requires initial access to internal networks.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ⚠️ Yes
Complexity: MEDIUM

Exploitation requires bypassing Chrome's sandbox and other security mitigations, but the vulnerability itself is remotely triggerable without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 140.0.7339.207 and later

Vendor Advisory: https://chromereleases.googleblog.com/2025/09/stable-channel-update-for-desktop_23.html

Restart Required: Yes

Instructions:

1. Open Chrome
2. Click the three-dot menu → Help → About Google Chrome
3. Chrome will automatically check for and install updates
4. Click 'Relaunch' to restart Chrome with the update applied

🔧 Temporary Workarounds

Disable JavaScript

all

Prevents exploitation by disabling JavaScript execution, but breaks most website functionality.

Use Site Isolation

all

Ensure Chrome's Site Isolation feature is enabled to limit impact of potential exploitation.

🧯 If You Can't Patch

  • Restrict access to untrusted websites using web filtering/proxy solutions
  • Implement application control to block Chrome execution until patched

🔍 How to Verify

Check if Vulnerable:

Check Chrome version: If version is less than 140.0.7339.207, the system is vulnerable.

Check Version:

chrome://version/ (in Chrome address bar) or 'google-chrome --version' (command line)

Verify Fix Applied:

Confirm Chrome version is 140.0.7339.207 or higher after applying update.

📡 Detection & Monitoring

Log Indicators:

  • Chrome crash reports with V8-related errors
  • Unexpected Chrome process termination

Network Indicators:

  • Requests to known malicious domains hosting exploit code
  • Unusual outbound connections from Chrome processes

SIEM Query:

source="chrome" AND (event_type="crash" OR message="*V8*" OR message="*heap corruption*")

🔗 References

📤 Share & Export