Active exploitation of CVE-2026-85046 in the Google Chromium V8 JavaScript engine allows for remote code execution (RCE) and a complete sandbox escape. The vulnerability leverages memory corruption—specifically type confusion or use-after-free flaws—to establish out-of-bounds (OOB) read/write primitives. By bypassing the Chromium multi-process security architecture through manipulated Inter-Process Communication (IPC), attackers can elevate privileges from the restricted renderer process to the host operating system. This critical flaw affects all Chromium-based browsers and has been added to the CISA Known Exploited Vulnerabilities (KEV) catalog. Immediate remediation requires updating to version 149.0.7827.102.103 for Windows/macOS or 149.0.7827.102 for Linux.
-
Vulnerability Mechanics: Memory Corruption
- Exploitation of type confusion or use-after-free flaws within the V8 engine core.
- Establishment of OOB read/write primitives to manipulate process memory.
- Achievement of initial RCE within the restricted renderer process.
-
Attack Vector: Sandbox Escape
- Bypass of Chromium's multi-process isolation via IPC primitives.
- Privilege escalation from the renderer sandbox to the host OS.
- Technical fixes and code path modifications documented in Chromium Issue 405143032.
-
Threat Landscape: Global Active Exploitation
- Confirmed zero-day exploitation in the wild targeting billions of users.
- Universal impact across the Chromium ecosystem, including Chrome, Microsoft Edge, Brave, and Opera.
- CISA KEV designation mandating urgent patching for federal and enterprise networks.
-
Regulatory and Compliance Impact
- Case study for EU Cyber Resilience Act (CRA) regarding rapid patch mandates.
- Increased pressure on vendors to minimize the window between discovery and deployment.
- Heightened compliance risks for organizations lacking emergency update cycles.
-
Detection and Remediation
- Mandatory update to v149.0.7827.102.103 (Windows/macOS) or v149.0.7827.102 (Linux).
- EDR monitoring for anomalous child processes spawned from browser threads (e.g.,
chrome.exespawningcmd.exeorsh). - Implementation of strict site isolation and memory protection policies to limit lateral movement.
Related posts
- news.ycombinator.com — Actively exploited sandbox RCE in all Chromium versions
- Cybersecurity News — Critical Chrome 0-Day Vulnerability Actively Exploited in the Wild
- Thenextweb
- Bleepingcomputer
- Hothardware
- Securityaffairs
- Menlosecurity
- Issues
- News