CVE-2025-13097
📋 TL;DR
This vulnerability allows a remote attacker to escape Chrome's sandbox protection through a crafted HTML page when DevTools is open. It affects users running Google Chrome versions before 136.0.7103.59. The attacker could potentially execute arbitrary code outside the sandbox constraints.
💻 Affected Systems
- Google Chrome
- Chromium-based browsers
📦 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 →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 system compromise with attacker gaining code execution at the user's privilege level, potentially leading to data theft, ransomware deployment, or persistent backdoor installation.
Likely Case
Limited sandbox escape allowing access to some system resources or files, but requiring user interaction (opening DevTools on malicious page).
If Mitigated
No impact if Chrome is updated or if users avoid opening DevTools on untrusted websites.
🎯 Exploit Status
Exploitation requires user to open DevTools on attacker-controlled page. No public exploit code available at disclosure.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: 136.0.7103.59 and later
Vendor Advisory: https://chromereleases.googleblog.com/2025/04/stable-channel-update-for-desktop_29.html
Restart Required: Yes
Instructions:
1. Open Chrome settings 2. Click 'About Chrome' 3. Allow update to download and install 4. Click 'Relaunch' when prompted
🔧 Temporary Workarounds
Disable DevTools Access
allPrevent users from opening DevTools via group policy or enterprise controls
Windows Registry: HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\DeveloperToolsDisabled = 1
macOS/Linux: Use Chrome Enterprise policies
Network Blocking
allBlock access to known malicious sites that could host exploit
Use firewall or proxy to block malicious domains
🧯 If You Can't Patch
- Disable Chrome DevTools via enterprise policies
- Use alternative browser until patch can be applied
- Educate users not to open DevTools on untrusted websites
🔍 How to Verify
Check if Vulnerable:
Check Chrome version in settings > About Chrome. If version is below 136.0.7103.59, system is vulnerable.Check Version:
chrome://version/ or 'google-chrome --version' in terminalVerify Fix Applied:
Confirm Chrome version is 136.0.7103.59 or higher after update.📡 Detection & Monitoring
Log Indicators:
- Chrome crash reports with DevTools-related errors
- Unusual process spawning from Chrome sandbox
Network Indicators:
- Requests to suspicious domains while DevTools is active
- Unusual outbound connections following DevTools usage
SIEM Query:
source="chrome_logs" AND (event="crash" OR event="sandbox_violation") AND process="chrome" AND component="devtools"