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-113317 Overview
CVE-2026-113317 is a memory corruption vulnerability in the Accessibility component of Google Chrome on macOS. The flaw affects Chrome versions prior to 156.0.8078.47 and is classified under [CWE-119] (Improper Restriction of Operations within the Bounds of a Memory Buffer). A remote attacker can trigger the condition by serving a crafted HTML page to a target user. Successful exploitation allows arbitrary code execution within the Chrome renderer sandbox. Google rated the Chromium security severity as High, with an assigned CVSS 3.1 score of 8.8.
Critical Impact
Remote attackers can execute arbitrary code inside the Chrome sandbox on macOS by luring a user to a crafted web page.
Affected Products
- Google Chrome on macOS prior to 156.0.8078.47
- Chromium-based builds packaging the vulnerable Accessibility component
- Apple macOS systems running the affected Chrome versions
Discovery Timeline
- 2026-10-20 - CVE-2026-113317 published to the National Vulnerability Database (NVD)
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113317
Vulnerability Analysis
The vulnerability resides in Chrome's Accessibility subsystem on macOS. Accessibility code bridges renderer-side DOM state with platform assistive technology APIs. Processing a crafted HTML page corrupts memory inside this layer. The corruption condition is reachable from untrusted web content without authentication. User interaction is required because the victim must load the attacker-controlled page. Once triggered, the attacker gains arbitrary code execution within the renderer sandbox boundary. The flaw maps to [CWE-119], indicating out-of-bounds access to a memory buffer. Sandbox-contained execution still provides a strong foothold for chaining with a sandbox escape to achieve full host compromise.
Root Cause
The root cause is improper handling of memory boundaries within the Accessibility component when parsing or applying attributes from a crafted HTML document. Specific technical details are tracked in Chromium Issue #555337558 and have not been publicly disclosed. CWE-119 covers conditions such as out-of-bounds reads, out-of-bounds writes, and use-after-free patterns inside buffer-backed structures.
Attack Vector
Exploitation requires a remote attacker to host or inject a crafted HTML page and convince a Chrome user on macOS to visit it. The attack surface is reachable over the network with low complexity and no privileges. The scope remains unchanged because execution is confined to the sandboxed renderer process, yet confidentiality, integrity, and availability are all affected within that boundary.
No public proof-of-concept is available at the time of writing. See the Google Chrome Stable Update advisory for vendor details.
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-113317
Indicators of Compromise
- Unexpected Chrome renderer process crashes on macOS endpoints coinciding with web browsing activity
- Child processes spawned by Google Chrome Helper (Renderer) that deviate from normal browser telemetry
- Outbound connections from Chrome renderer processes to low-reputation or newly registered domains hosting HTML payloads
Detection Strategies
- Inventory installed Chrome versions on macOS fleet and flag any build older than 156.0.8078.47
- Correlate browser crash reports and ReportCrash events on macOS with URLs loaded immediately prior to the crash
- Hunt for anomalous memory allocation patterns or exceptions originating from Chrome Accessibility code paths
Monitoring Recommendations
- Enable endpoint telemetry for process creation, module loads, and crash events on macOS browser processes
- Forward Chrome enterprise reporting logs to a SIEM for version compliance tracking
- Alert on Chrome renderer processes writing to unusual file system locations or spawning shell interpreters
How to Mitigate CVE-2026-113317
Immediate Actions Required
- Update Google Chrome on all macOS endpoints to version 156.0.8078.47 or later
- Validate that automatic updates are enabled and verify effective version post-deployment
- Prioritize patching for users who browse untrusted content or operate in high-risk roles
Patch Information
Google released the fix in the Chrome Stable channel. Install Chrome 156.0.8078.47 or newer on macOS. Full details are available in the Google Chrome Stable Update advisory. Chromium tracking is published at Chromium Issue #555337558.
Workarounds
- Restrict browsing to trusted sites via enterprise policy until the patch is applied
- Deploy site isolation and strict HTTPS enforcement through Chrome enterprise policies
- Consider temporarily disabling Chrome's integration with macOS assistive technologies for users who do not require it
# Verify the installed Chrome version on macOS
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
# Enforce minimum version via MDM-managed Chrome enterprise policy (example)
# Deploy a configuration profile that enables and audits automatic updates
defaults write com.google.Keystone.Agent checkInterval -int 3600
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

