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-113165 Overview
CVE-2026-113165 is a use-after-free vulnerability in the Core component of Google Chrome on macOS. The flaw affects Chrome versions prior to 156.0.8078.47 and allows a remote attacker to execute arbitrary code inside the Chrome sandbox. Exploitation requires a user to visit a crafted HTML page. Google classified the Chromium security severity as Medium, while the National Vulnerability Database (NVD) assigns a higher score due to confidentiality, integrity, and availability impact. The vulnerability is tracked under CWE-416: Use After Free.
Critical Impact
A remote attacker who convinces a user to load a malicious web page can execute arbitrary code within the Chrome renderer sandbox on macOS, enabling the first stage of a browser compromise chain.
Affected Products
- Google Chrome for macOS versions prior to 156.0.8078.47
- Apple macOS (host platform for the vulnerable Chrome build)
- Chromium-based browsers that incorporate the vulnerable Core component
Discovery Timeline
- 2026-10-20 - CVE-2026-113165 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113165
Vulnerability Analysis
The vulnerability is a use-after-free condition in Chrome's Core component. Use-after-free bugs occur when a program references memory after it has been freed. The freed allocation can be reused by attacker-controlled data, causing the dangling pointer to operate on crafted state. In Chrome, this typically produces type confusion in C++ objects, enabling arbitrary read, arbitrary write, or control-flow hijacking within the renderer process.
Exploitation requires user interaction. A victim must load a crafted HTML page under attacker control. Once triggered, the attacker gains arbitrary code execution inside the Chrome sandbox. The sandbox limits direct access to the operating system, but renderer-level execution is a common stepping stone for sandbox-escape chains that lead to full host compromise on macOS.
Root Cause
The root cause is improper lifetime management of a heap-allocated object in Chrome's Core subsystem. A code path releases an object while another reference remains live. Subsequent operations dereference the stale pointer, operating on memory that may have been reclaimed and populated by attacker-controlled content delivered through the crafted HTML page.
Attack Vector
The attack is network-based and requires no privileges. An attacker hosts a malicious page or injects malicious content into a page the victim visits. Delivery channels include phishing links, malvertising, compromised third-party scripts, and watering-hole attacks. User interaction is limited to loading the page in a vulnerable Chrome build on macOS.
See Chromium Issue Tracker #553163770 for technical details.
No verified public proof-of-concept has been released at the time of writing.
Detection Methods for CVE-2026-113165
Indicators of Compromise
- Chrome renderer process crashes on macOS endpoints running builds earlier than 156.0.8078.47, particularly crashes referencing freed heap objects.
- Unexpected child processes spawned by Google Chrome Helper (Renderer) following navigation to an untrusted site.
- Outbound connections from Chrome helper processes to newly registered or low-reputation domains after loading HTML content.
Detection Strategies
- Inventory installed Chrome versions across macOS fleets and flag any instance below 156.0.8078.47.
- Monitor the macOS Unified Log and crash reporter for com.google.Chrome.helper segmentation faults and EXC_BAD_ACCESS exceptions tied to browsing activity.
- Correlate browser process anomalies with proxy and DNS telemetry to identify pages that trigger renderer instability.
Monitoring Recommendations
- Enable endpoint detection and response (EDR) telemetry for Chrome helper process creation, memory anomalies, and child-process execution on macOS.
- Forward browser crash telemetry and web proxy logs to a centralized data lake for correlation and retrospective hunting.
- Track Google Chrome release channel announcements and incorporate the stable channel update into vulnerability feeds.
How to Mitigate CVE-2026-113165
Immediate Actions Required
- Update Google Chrome on macOS to version 156.0.8078.47 or later across all managed endpoints.
- Enforce automatic Chrome updates through MDM policy to prevent version drift.
- Restrict high-risk browsing from endpoints that cannot be patched immediately using web filtering or isolation.
Patch Information
Google addressed CVE-2026-113165 in the Chrome stable channel for desktop. Administrators should deploy Chrome 156.0.8078.47 or later on macOS. Full release details are published in the Google Chrome Stable Channel Update for Desktop and the Chromium Issue Tracker #553163770.
Workarounds
- Block navigation to untrusted or unknown web destinations through secure web gateways until patching completes.
- Deploy browser isolation for high-risk user groups such as executives, developers, and finance staff.
- Disable or restrict third-party content and advertisements through enterprise ad-blocking policies to reduce malvertising exposure.
# Verify installed Chrome version on macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
# Example MDM-managed update enforcement (Jamf/Munki)
# Pin minimum allowed Chrome version to 156.0.8078.47
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

