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-113219 Overview
CVE-2026-113219 is a memory corruption vulnerability in the Contacts component of Google Chrome. The flaw affects Chrome versions prior to 156.0.8078.47. A remote attacker can execute arbitrary code inside the Chrome sandbox by convincing a user to visit a crafted HTML page. The weakness is categorized under CWE-119, improper restriction of operations within the bounds of a memory buffer. Google rated the Chromium security severity as Medium, while the National Vulnerability Database (NVD) assigns a higher CVSS base score reflecting the arbitrary code execution impact.
Critical Impact
Remote attackers can execute arbitrary code inside the Chrome renderer sandbox through a single malicious web page, enabling drive-by compromise of users who browse attacker-controlled or compromised sites.
Affected Products
- Google Chrome Desktop versions prior to 156.0.8078.47
- Chromium-based builds incorporating the vulnerable Contacts component
- All supported desktop platforms (Windows, macOS, Linux) running pre-patch Chrome
Discovery Timeline
- 2026-10-20 - CVE-2026-113219 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113219
Vulnerability Analysis
The vulnerability resides in Chrome's Contacts component, which handles the browser's Contact Picker API. This API allows web pages to request access to user contact information with permission. The bug produces memory corruption when the component processes attacker-controlled input delivered through a crafted HTML page. Successful exploitation yields arbitrary code execution within the Chrome sandbox process. The sandbox limits direct host impact, but code execution inside the renderer provides a strong foothold for chaining with a sandbox escape to achieve full system compromise.
Root Cause
The root cause is improper restriction of operations within the bounds of a memory buffer, as classified by CWE-119. The Contacts implementation fails to correctly validate memory boundaries while handling data structures associated with contact-picker interactions. Attackers manipulate these structures from JavaScript running in the page, triggering an out-of-bounds memory operation that corrupts adjacent heap state. Full technical analysis is tracked in the Chromium Issue Tracker Entry.
Attack Vector
Exploitation requires network delivery and user interaction. An attacker hosts a crafted HTML page, then lures the victim to open it through phishing, malvertising, or compromised legitimate sites. When the page loads, JavaScript invokes the Contacts component in a way that triggers the memory corruption. Code then executes inside the renderer process, which is confined by the Chrome sandbox but can be chained with additional vulnerabilities for privilege escalation.
No public proof-of-concept exploit is listed for CVE-2026-113219 at this time, and the issue is not present on the CISA Known Exploited Vulnerabilities catalog. See the Chromium Issue Tracker Entry for additional technical context.
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 AttemptsDetection Methods for CVE-2026-113219
Indicators of Compromise
- Chrome renderer process crashes or unexpected restarts shortly after visiting an unfamiliar page, often logged under chrome_crashpad
- Child processes spawned by chrome.exe that are not standard Chrome helpers, especially shells or scripting interpreters
- Outbound network connections from the Chrome renderer to uncategorized or newly registered domains following a web browsing session
Detection Strategies
- Inventory Chrome installations across endpoints and flag any version earlier than 156.0.8078.47
- Correlate browser crash telemetry with web navigation history to surface suspicious page loads that preceded a renderer crash
- Alert on Chrome processes writing to disk locations outside their normal profile and cache directories
Monitoring Recommendations
- Ingest endpoint process-tree and network telemetry into a central data lake and apply behavioral analytics to Chrome activity
- Monitor DNS and proxy logs for traffic patterns consistent with exploit-kit infrastructure serving crafted HTML
- Track Chrome auto-update status at scale and alert when hosts fall behind the current stable channel release
How to Mitigate CVE-2026-113219
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later on all desktop endpoints
- Verify that Chrome auto-update is enabled and functioning, especially on managed and air-gapped systems
- Restart Chrome after the update to ensure the patched binary is loaded into memory
Patch Information
Google released the fix in the Chrome stable channel update documented in the Google Chrome Desktop Update advisory. Administrators managing Chrome through enterprise policy should push the updated MSI or PKG and confirm the deployed BrowserVersion meets or exceeds 156.0.8078.47.
Workarounds
- Restrict use of the Contacts component through enterprise policy where business workflows do not require the Contact Picker API
- Deploy content filtering and DNS protection to block known malicious domains that could host crafted exploit pages
- Enforce the use of site isolation and strict sandboxing policies in Chrome to limit the impact of renderer compromise
# Verify installed Chrome version on Windows endpoints
reg query "HKLM\Software\Google\Update\Clients\{8A69D345-D564-463C-AFF1-A69D9E530F96}" /v pv
# Verify installed Chrome version on macOS endpoints
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
# Verify installed Chrome version on Linux endpoints
google-chrome --version
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

