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

CVE-2026-113326: Google Chrome Information Disclosure Flaw

CVE-2026-113326 is an information disclosure vulnerability in Google Chrome on Windows that allows attackers to read memory inside the sandbox through a crafted HTML page. This post explains its impact, affected versions, and mitigation steps.

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-113326 Overview

CVE-2026-113326 is a memory corruption vulnerability in the Core component of Google Chrome on Windows. The flaw affects Chrome versions prior to 156.0.8078.47 and allows a remote attacker to read memory inside the browser sandbox using a crafted HTML page. Google classifies the Chromium security severity as Medium.

Successful exploitation requires user interaction, specifically visiting an attacker-controlled web page. The weakness is cataloged under [CWE-119] (Improper Restriction of Operations within the Bounds of a Memory Buffer).

Critical Impact

Remote attackers can read sensitive memory contents from within the Chrome sandbox by luring users to malicious HTML pages, exposing data such as credentials, tokens, or browsing artifacts.

Affected Products

  • Google Chrome on Windows prior to version 156.0.8078.47
  • Microsoft Windows (host platform)
  • Chromium-based engine Core component

Discovery Timeline

  • 2026-10-20 - CVE-2026-113326 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-113326

Vulnerability Analysis

The vulnerability resides in Chrome's Core component on Windows. A crafted HTML page triggers a memory handling flaw that permits unauthorized reads of adjacent memory within the renderer sandbox. The result is an information disclosure primitive confined to the sandboxed process, not direct code execution on the host.

Attackers typically pair such primitives with additional bugs to escalate impact. Leaked memory can include pointers useful for defeating Address Space Layout Randomization (ASLR), browser session data, or in-process secrets. The confidentiality impact is high while integrity and availability remain unaffected.

Root Cause

The underlying weakness is improper restriction of operations within the bounds of a memory buffer [CWE-119]. Chrome's Core code fails to correctly validate buffer boundaries when processing content delivered through a crafted HTML page. This mishandling exposes bytes outside the intended allocation to attacker-controlled script.

Attack Vector

Exploitation requires a user to load a malicious HTML page in a vulnerable Chrome build. The attacker hosts crafted markup or script that forces the Core component to perform the unsafe memory operation. No authentication is required, and the attack is delivered over the network. The exploit executes inside the renderer sandbox, limiting direct host compromise.

No public proof-of-concept has been published, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Technical specifics are tracked in the Chromium Issue Tracker Entry.

Detection Methods for CVE-2026-113326

Indicators of Compromise

  • Browser telemetry showing Chrome renderer processes crashing or exhibiting anomalous memory read patterns after visiting unfamiliar sites
  • Outbound connections to newly registered or low-reputation domains hosting HTML content with heavy script-driven memory allocation
  • Chrome versions below 156.0.8078.47 present on Windows endpoints in software inventory scans

Detection Strategies

  • Inventory Chrome installations across Windows endpoints and flag any build below 156.0.8078.47
  • Monitor web proxy and DNS logs for traffic to domains serving malicious HTML payloads targeting Chromium renderers
  • Correlate renderer process anomalies with recent navigation events to identify suspicious page loads

Monitoring Recommendations

  • Enable endpoint telemetry that records browser process creation, child process relationships, and crash events
  • Collect Chrome update status via management tooling to verify auto-update is functioning on all managed devices
  • Alert on execution of unexpected binaries spawned by chrome.exe renderer processes

How to Mitigate CVE-2026-113326

Immediate Actions Required

  • Update Google Chrome on all Windows endpoints to version 156.0.8078.47 or later
  • Verify Chrome's auto-update mechanism is enabled and reporting successful installations through enterprise management
  • Restart Chrome after the update to ensure the patched binaries are loaded into active sessions

Patch Information

Google released the fix in the Chrome stable channel update that advanced the Windows build to 156.0.8078.47. Refer to the Google Chrome Stable Update release notes for full details and additional security fixes in the same release.

Workarounds

  • Restrict browsing to trusted sites using enterprise web filtering until patching completes
  • Deploy Chrome Enterprise policies that disable or limit high-risk web features on unpatched systems
  • Use application allowlisting to prevent execution of secondary payloads delivered via browser exploitation chains
bash
# Verify installed Chrome version on Windows
reg query "HKLM\Software\Google\Update\Clients\{8A69D345-D564-463C-AFF1-A69D9E530F96}" /v pv

# Force Chrome update check via Group Policy management
gpupdate /force

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.