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

CVE-2026-113214: Google Chrome RCE Vulnerability

CVE-2026-113214 is a remote code execution flaw in Google Chrome FullScreen that enables attackers to execute arbitrary code in the sandbox via crafted HTML. This post 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-113214 Overview

CVE-2026-113214 is an improper input validation vulnerability [CWE-20] in the FullScreen component of Google Chrome. The flaw affects Chrome versions prior to 156.0.8078.47. A remote attacker can exploit this issue by serving a crafted HTML page to a target user. Successful exploitation allows arbitrary code execution within the Chrome sandbox.

The vulnerability requires user interaction, meaning the victim must visit or be redirected to an attacker-controlled page. Google tracks this issue in Chromium bug #506148052 and rates the Chromium security severity as Low, though the NVD scoring reflects a higher technical impact.

Critical Impact

Remote attackers can execute arbitrary code inside the Chrome sandbox through a crafted HTML page, enabling browser-based compromise of end-user systems.

Affected Products

  • Google Chrome versions prior to 156.0.8078.47 (Desktop)
  • Chromium-based browsers inheriting the vulnerable FullScreen implementation
  • All operating systems where vulnerable Chrome builds are deployed (Windows, macOS, Linux)

Discovery Timeline

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

Technical Details for CVE-2026-113214

Vulnerability Analysis

The vulnerability resides in the FullScreen component of Google Chrome, which manages transitions between windowed and fullscreen rendering modes. Improper input validation [CWE-20] permits a crafted HTML page to supply malformed data that the FullScreen logic processes without adequate checks.

When the browser handles the malicious input, the flaw can be chained to achieve arbitrary code execution inside the renderer sandbox. The attacker gains code execution confined to Chrome's sandbox boundary, but this foothold can serve as a stepping stone when combined with a separate sandbox escape.

User interaction is required for exploitation. The target must load the crafted page in a vulnerable Chrome build. Technical specifics are tracked in Chromium issue #506148052.

Root Cause

The root cause is insufficient validation of attacker-controlled input processed by the FullScreen subsystem. Chrome's rendering pipeline accepts data that falls outside expected boundaries or formats, allowing attacker-supplied content to influence execution paths. The flaw aligns with the CWE-20 category of improper input validation.

Attack Vector

Exploitation occurs over the network through a web browsing session. The attacker hosts a crafted HTML page or injects malicious content into a page the victim visits. When the victim loads the page in an unpatched Chrome build, the FullScreen handler processes the malicious input and triggers code execution within the sandbox.

The vulnerability does not require authentication. It does require user interaction, typically a page visit or click, and does not need prior access to the target system. See the Chromium Issue Tracker #506148052 for technical details once the bug is unrestricted.

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-113214

Indicators of Compromise

  • Chrome renderer processes spawning unexpected child processes or performing unusual file system access immediately after page navigation
  • Browser crash reports or renderer sandbox violations originating from pages invoking the FullScreen API
  • Outbound connections from Chrome renderer processes to attacker-controlled infrastructure following visits to untrusted sites

Detection Strategies

  • Inventory installed Chrome versions across managed endpoints and flag any build older than 156.0.8078.47
  • Correlate web proxy logs with endpoint telemetry to identify users visiting pages that trigger FullScreen transitions followed by anomalous process behavior
  • Monitor EDR telemetry for Chrome renderer processes exhibiting memory anomalies, injection attempts, or sandbox escape patterns

Monitoring Recommendations

  • Enable browser crash reporting and forward reports to a central analytics system to spot clusters of FullScreen-related crashes
  • Track Chrome update compliance through endpoint management tooling and alert on devices lagging behind the current stable channel
  • Review DNS and HTTP(S) proxy logs for connections to newly observed or low-reputation domains correlated with Chrome activity

How to Mitigate CVE-2026-113214

Immediate Actions Required

  • Update Google Chrome to version 156.0.8078.47 or later on all managed endpoints
  • Push the updated stable channel build through enterprise management tools such as Chrome Browser Cloud Management or group policy
  • Restart Chrome on all endpoints to ensure the patched binaries load into active browser sessions
  • Validate patch deployment by querying installed browser versions through endpoint management or EDR inventory

Patch Information

Google addressed CVE-2026-113214 in the Chrome Stable Channel update to version 156.0.8078.47. Details are documented in the Google Chrome Stable Update advisory. The fix is tracked in Chromium Issue Tracker #506148052. Apply the update across Windows, macOS, and Linux fleets without delay.

Workarounds

  • Restrict browsing to trusted sites through web filtering or allowlisting until patches are deployed
  • Disable or restrict access to the Fullscreen API through enterprise browser policies where feasible
  • Deploy site isolation and strict renderer sandboxing settings to reduce the blast radius of a successful renderer compromise
  • Educate users to avoid loading untrusted pages that request fullscreen transitions
bash
# Verify Chrome version on Linux endpoints
google-chrome --version

# Enterprise policy example (Windows registry) to force update channel
# HKLM\SOFTWARE\Policies\Google\Update
#   TargetChannel = "stable"
#   UpdateDefault = 1

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.