CVE-2025-13223

8.8 HIGH CISA KEV

📋 TL;DR

A type confusion vulnerability in Chrome's V8 JavaScript engine allows attackers to trigger heap corruption by tricking the engine into treating one data type as another. This affects all users running vulnerable versions of Google Chrome. Successful exploitation could lead to arbitrary code execution.

💻 Affected Systems

Products:
  • Google Chrome
  • Chromium-based browsers
Versions: Versions prior to 142.0.7444.175
Operating Systems: Windows, macOS, Linux, Android, iOS
Default Config Vulnerable: ⚠️ Yes
Notes: All standard Chrome installations are vulnerable. Extensions or security settings don't mitigate this.

📦 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

Remote code execution with the same privileges as the Chrome process, potentially leading to full system compromise, data theft, or ransomware deployment.

🟠

Likely Case

Browser crash (denial of service) or limited code execution within the sandboxed renderer process.

🟢

If Mitigated

Browser crash with no data loss if sandboxing holds, or blocked execution if exploit detection triggers.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

CISA confirms known exploitation. Exploit requires user to visit a malicious webpage.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 142.0.7444.175 and later

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

Restart Required: Yes

Instructions:

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

🔧 Temporary Workarounds

Disable JavaScript

all

Prevents execution of malicious JavaScript that could trigger the vulnerability

Use Site Isolation

all

Enforces process separation between websites to limit exploit impact

Navigate to chrome://flags/#site-isolation-trial-opt-out and set to 'Disabled'

🧯 If You Can't Patch

  • Use alternative browsers until patching is possible
  • Implement network filtering to block known malicious domains hosting exploits

🔍 How to Verify

Check if Vulnerable:

Check Chrome version: Open Chrome → three-dot menu → Help → About Google Chrome. If version is below 142.0.7444.175, you're vulnerable.

Check Version:

On Windows: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version
On macOS: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
On Linux: google-chrome --version

Verify Fix Applied:

Confirm Chrome version is 142.0.7444.175 or higher after update.

📡 Detection & Monitoring

Log Indicators:

  • Chrome crash reports with V8-related errors
  • Unexpected renderer process terminations

Network Indicators:

  • Connections to domains hosting known exploit kits
  • Unusual outbound traffic from Chrome processes

SIEM Query:

source="chrome" AND (event_type="crash" OR process_name="chrome.exe") AND message="V8"

🔗 References

📤 Share & Export