Skip to main content
Vulnerability Database/CVE-2026-113243

CVE-2026-113243: Google Chrome DOM Memory RCE Vulnerability

CVE-2026-113243 is a memory corruption flaw in Google Chrome's DOM that enables remote code execution within the sandbox via malicious HTML pages. This article covers technical details, affected versions, and mitigation.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-113243 Overview

CVE-2026-113243 is a memory corruption vulnerability in the Document Object Model (DOM) implementation of Google Chrome prior to version 156.0.8078.47. A remote attacker can trigger the flaw by serving a crafted HTML page to a victim, potentially leading to arbitrary code execution inside the Chrome sandbox. The weakness is categorized under CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer. Google Chrome tracks the issue with a Chromium severity rating of Medium, while the National Vulnerability Database records it as High. User interaction is required, as the victim must load the malicious page in Chrome.

Critical Impact

Successful exploitation allows remote attackers to execute arbitrary code within the Chrome renderer sandbox, providing a foothold for subsequent sandbox escape chains.

Affected Products

  • Google Chrome Desktop versions prior to 156.0.8078.47
  • Chromium-based browsers that have not integrated the upstream fix
  • Any platform (Windows, macOS, Linux) running a vulnerable Chrome build

Discovery Timeline

  • 2026-10-20 - CVE-2026-113243 published to the National Vulnerability Database
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-113243

Vulnerability Analysis

The vulnerability resides in the DOM subsystem of Chrome's Blink rendering engine. Memory corruption in the DOM typically occurs when object lifetimes are managed incorrectly across script-triggered mutations, enabling access to memory that has been freed, resized, or reused. An attacker who controls page content can orchestrate specific DOM operations through JavaScript to corrupt renderer process memory.

Once memory state is corrupted, the attacker can steer execution flow inside the renderer sandbox. The Chrome sandbox limits direct host impact, however renderer-level code execution is routinely chained with sandbox escape vulnerabilities for full compromise. The flaw requires user interaction, meaning the victim must visit a page under attacker control or load attacker-supplied HTML.

Root Cause

The root cause is a memory safety defect in DOM handling that falls under CWE-119, improper restriction of operations within the bounds of a memory buffer. Public details are limited while Google restricts access to the Chromium Issue Tracker #553147798 to allow patch adoption.

Attack Vector

The attack vector is network-based and requires only that a user navigate to a crafted HTML page. Delivery mechanisms include phishing links, malicious advertising, compromised websites, and iframe injection on third-party sites. No authentication or elevated privileges are needed on the target system.

No verified public proof-of-concept is available at the time of publication. Technical details are described in prose only; see the Chrome Stable Update Announcement for vendor guidance.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-113243

Indicators of Compromise

  • Chrome renderer process crashes with memory access violations shortly after loading external pages
  • Outbound connections from Chrome child processes to uncommon or newly registered domains
  • Unexpected child processes spawned by chrome.exe following browsing activity
  • Browser telemetry showing Chrome versions older than 156.0.8078.47 in the fleet

Detection Strategies

  • Inventory installed Chrome versions across managed endpoints and flag any build earlier than 156.0.8078.47
  • Monitor crash reports and WER (Windows Error Reporting) events for renderer process faults in chrome.dll DOM code paths
  • Correlate web proxy logs with endpoint telemetry to identify users who visited suspicious domains immediately before renderer crashes

Monitoring Recommendations

  • Alert on anomalous process behavior originating from Chrome renderer processes, including memory region allocation and shellcode indicators
  • Track browser version compliance through endpoint management tooling and generate exceptions for stale installs
  • Ingest browser crash telemetry and proxy logs into a centralized data lake for correlation and retrospective hunting

How to Mitigate CVE-2026-113243

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later on all desktop endpoints
  • Restart Chrome after update to ensure the patched binaries are loaded into memory
  • Push the update through enterprise management (Google Chrome Enterprise, Intune, Jamf) to accelerate rollout
  • Validate that Chromium-based downstream browsers in use have incorporated the upstream fix

Patch Information

Google released the fix in the Stable channel update documented in the Chrome Stable Update Announcement. Administrators should confirm the installed version is at least 156.0.8078.47 across Windows, macOS, and Linux clients. Chromium downstreams including Edge, Brave, Opera, and Vivaldi should be updated once their vendors publish aligned builds.

Workarounds

  • Enforce the SitePerProcess policy to maintain strict renderer isolation and reduce cross-origin exposure
  • Restrict browsing to known-good domains through web proxy allowlists until patching completes
  • Disable JavaScript execution on untrusted origins using Chrome enterprise policy where operationally feasible
  • Deploy browser isolation technology for high-risk users who browse the open web
bash
# Verify Chrome version on Windows endpoints
reg query "HKLM\Software\Google\Update\Clients\{8A69D345-D564-463C-AFF1-A69D9E530F96}" /v pv

# Verify Chrome version on macOS/Linux
google-chrome --version
# Expected output: Google Chrome 156.0.8078.47 or later

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.