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-113047 Overview
CVE-2026-113047 is a memory corruption vulnerability in the BrowserTag component of Google Chrome prior to version 156.0.8078.47. A remote attacker can exploit the flaw by serving a crafted HTML page to a target user. Successful exploitation allows the attacker to read memory inside the Chrome sandbox, leading to disclosure of sensitive in-process data. The weakness is classified under [CWE-119] (Improper Restriction of Operations within the Bounds of a Memory Buffer). Chromium rates the underlying security severity as Low, while the NVD assigns a medium CVSS score reflecting the network attack vector and confidentiality impact.
Critical Impact
A crafted HTML page can trigger memory corruption in BrowserTag, enabling a remote attacker to read sandboxed memory contents and potentially extract sensitive browser state.
Affected Products
- Google Chrome versions prior to 156.0.8078.47 (Desktop, Stable channel)
- Chromium-based builds incorporating the vulnerable BrowserTag implementation
- Downstream browsers that have not merged the upstream Chromium fix
Discovery Timeline
- 2026-10-20 - CVE-2026-113047 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113047
Vulnerability Analysis
The vulnerability resides in Chrome's BrowserTag component, which handles embedded browsing contexts within a page. Processing a crafted HTML page triggers a memory corruption condition that lets attacker-controlled logic reach adjacent memory regions. The out-of-bounds access returns data from the renderer or browser process allocation space inside the sandbox. Exploitation requires user interaction, specifically visiting or rendering the malicious HTML page. The resulting primitive is a memory read, not code execution, so attackers primarily gain information disclosure rather than direct control of the host.
Root Cause
The root cause maps to [CWE-119], improper restriction of operations within the bounds of a memory buffer. The BrowserTag code path fails to correctly validate buffer sizes or offsets before accessing memory. Attacker-controlled HTML attributes or script interactions drive the component into a state where reads cross the intended allocation boundary. See Chromium Issue #553267541 for the upstream tracker.
Attack Vector
Exploitation is network-based and requires user interaction. The attacker hosts a crafted HTML page and lures the victim to open it in a vulnerable Chrome build. The page issues DOM operations against BrowserTag that trigger the memory corruption. The attack does not require authentication or elevated privileges. Because the read is bounded by the sandbox, it does not grant arbitrary code execution on its own, but attackers can chain the leak with other flaws to defeat memory layout defenses.
No verified public proof-of-concept is available at the time of publication. Technical details are tracked in the referenced Chromium issue.
Detection Methods for CVE-2026-113047
Indicators of Compromise
- Browser telemetry showing Chrome versions earlier than 156.0.8078.47 rendering untrusted HTML pages
- Web proxy or DNS logs recording connections to newly registered domains delivering HTML with unusual BrowserTag, <embed>, or nested browsing-context constructs
- Renderer process crashes or anomalous memory access patterns in Chrome crash telemetry correlated with specific pages
Detection Strategies
- Inventory endpoints and extract installed Chrome versions, flagging any instance below 156.0.8078.47
- Hunt web gateway logs for HTML payloads containing suspicious embedded browsing contexts delivered from low-reputation hosts
- Correlate endpoint crash reports (chrome.exe renderer crashes) with the browsing history to identify candidate exploitation attempts
Monitoring Recommendations
- Enable centralized Chrome update reporting and alert on hosts that fall behind the fixed version
- Forward browser crash and security event telemetry to the SIEM for correlation with proxy and EDR data
- Monitor outbound traffic for data exfiltration patterns following visits to untrusted sites, since the primitive is a memory read
How to Mitigate CVE-2026-113047
Immediate Actions Required
- Update Google Chrome Desktop to version 156.0.8078.47 or later on all managed endpoints
- Restart Chrome after the update to ensure the patched binary is loaded in all renderer and browser processes
- Audit Chromium-based browsers and embedded WebView components for merge status of the upstream fix
Patch Information
Google addressed CVE-2026-113047 in the Chrome Stable channel release documented in the Google Chrome Stable Update advisory. The fix ships in Chrome 156.0.8078.47 for Desktop. Enterprise administrators should push the update through Google Update, managed software distribution, or MDM policies. Verify deployment by checking chrome://version on representative hosts after rollout.
Workarounds
- Enforce strict web filtering policies that block access to untrusted or newly observed domains serving HTML content
- Deploy browser group policies that restrict rendering of embedded content from untrusted origins where feasible
- Instruct users to avoid clicking links from unverified sources until patch deployment is confirmed across the fleet
# Verify Chrome version on Windows managed 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: 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

