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

CVE-2026-113329: Google Chrome Out of Bounds Read Vulnerability

CVE-2026-113329 is an out of bounds read flaw in Google Chrome Installer on Mac that allows attackers to read memory within the sandbox through malicious web pages. This article 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-113329 Overview

CVE-2026-113329 is an out-of-bounds read vulnerability [CWE-125] in the Installer component of Google Chrome on macOS. The flaw affects Chrome versions prior to 156.0.8078.47. A remote attacker can exploit the vulnerability by serving a crafted HTML page to a target user. Successful exploitation allows the attacker to read memory contents inside the Chrome sandbox. Google classified the Chromium security severity as Medium.

Critical Impact

Remote attackers can read sensitive process memory within the sandbox by luring users to a malicious HTML page, potentially exposing data useful for further exploitation.

Affected Products

  • Google Chrome on macOS prior to 156.0.8078.47
  • Apple macOS systems running vulnerable Chrome builds
  • Chromium-based deployments on macOS inheriting the affected Installer code

Discovery Timeline

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

Technical Details for CVE-2026-113329

Vulnerability Analysis

The vulnerability resides in the Installer component of Chrome on macOS. The code reads beyond the bounds of an allocated buffer when processing attacker-influenced input. This behavior falls under [CWE-125: Out-of-bounds Read]. The read occurs within the Chrome sandbox, which limits what an attacker can retrieve. However, leaked memory may contain pointers, tokens, or heap layout data useful for chaining with other vulnerabilities. Exploitation requires user interaction, specifically visiting a crafted HTML page. The confidentiality impact is high, while integrity and availability are not affected.

Root Cause

The root cause is missing or insufficient boundary validation in the Installer code path. When parsing structured data from a crafted HTML page, the component dereferences memory outside the intended buffer range. See the Chromium Issue Tracker Entry for upstream fix details.

Attack Vector

The attack vector is network-based and requires user interaction. An attacker hosts a malicious HTML page and lures the target to visit it using phishing, malvertising, or a compromised site. When the page triggers the vulnerable Installer code path, the browser reads out-of-bounds memory. The attacker then exfiltrates that memory to the attacker-controlled page. No authentication is required.

No verified proof-of-concept code is publicly available. Technical details are limited to the vendor advisories listed in the Chrome Release Update Blog.

Detection Methods for CVE-2026-113329

Indicators of Compromise

  • Chrome browser crash reports on macOS referencing the Installer component or out-of-bounds memory access
  • Outbound HTTP(S) requests from Chrome containing unexpected binary blobs following visits to untrusted sites
  • Chrome process versions on macOS endpoints reporting a build earlier than 156.0.8078.47

Detection Strategies

  • Inventory installed Chrome versions on all macOS endpoints and flag any build below 156.0.8078.47
  • Correlate browser crash telemetry with recent navigation events to untrusted or newly registered domains
  • Monitor DNS and web proxy logs for connections to domains associated with exploit kits targeting Chromium flaws

Monitoring Recommendations

  • Enable Chrome enterprise reporting to centralize version and crash telemetry
  • Alert on Chrome processes spawning unexpected child processes on macOS hosts
  • Track user navigation to low-reputation domains correlated with Chrome renderer anomalies

How to Mitigate CVE-2026-113329

Immediate Actions Required

  • Update Google Chrome on all macOS endpoints to 156.0.8078.47 or later
  • Restart Chrome after update to ensure the patched Installer code is loaded
  • Verify managed deployments by auditing Chrome versions through MDM or endpoint management tooling

Patch Information

Google released the fix in the Chrome stable channel update documented in the Chrome Release Update Blog. The fixed version is 156.0.8078.47 for macOS. The upstream Chromium fix is tracked in the Chromium Issue Tracker Entry.

Workarounds

  • Restrict browsing to trusted sites until the patch is deployed across the fleet
  • Use web filtering or DNS protection to block newly registered and low-reputation domains
  • Enable automatic Chrome updates on managed macOS devices to shorten exposure windows for future issues
bash
# Verify installed Chrome version on macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version

# Force an update check via the Chrome update helper
/Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle/Contents/Resources/GoogleSoftwareUpdateAgent.app/Contents/MacOS/GoogleSoftwareUpdateAgent -runMode oneshot

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.