Loading vulnerability…
Sandboxed Code Execution in Google Chrome DOM
CVE-2026-110913 is a high-severity memory corruption vulnerability in the DOM component of Google Chrome before version 155.0.8059.84. Processing a crafted HTML page can allow a remote attacker to execute arbitrary code inside the browser sandbox. Chromium is also affected. The specific vulnerable function and underlying memory corruption mechanism have not been disclosed.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows arbitrary code execution within the browser sandbox, compromising the affected execution context. The vulnerability alone does not establish sandbox escape or unrestricted access to the host operating system.
If you can’t patch tonight, do this now.
Until the update is installed, avoid opening untrusted HTML content. This reduces exposure but does not replace patching; no vulnerability-specific workaround is documented.
Patch, then assume compromise.
Update Google Chrome to version 155.0.8059.84 or later, using the fixed release appropriate for the platform; the announced Windows and macOS releases include 155.0.8059.84/.85. Restart Chrome to complete installation and verify the installed version. For Chromium, install the distribution-provided security update incorporating version 155.0.8059.84 or later. Fedora and EPEL update instructions additionally require logging out and back in after installation.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
28 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.