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-113144 Overview
CVE-2026-113144 is a memory corruption vulnerability in the Speech component of Google Chrome. The flaw affects versions prior to 156.0.8078.47 and allows a remote attacker to read memory inside the sandbox through a crafted HTML page. Google rates the Chromium security severity as Medium. Exploitation requires user interaction, specifically that a victim visits a malicious page. The vulnerability maps to [CWE-119], improper restriction of operations within the bounds of a memory buffer. No active exploitation has been reported, and the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
Critical Impact
A remote attacker can read sensitive in-process memory from within the Chrome renderer sandbox by luring a user to a crafted web page, enabling information disclosure of browser data.
Affected Products
- Google Chrome versions prior to 156.0.8078.47 (Desktop Stable channel)
- Chromium-based browsers that incorporate the vulnerable Speech component
- All platforms where the affected Chrome build is distributed
Discovery Timeline
- 2026-10-20 - CVE-2026-113144 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-113144
Vulnerability Analysis
The vulnerability resides in the Speech subsystem of Google Chrome, which handles Web Speech API functionality including speech recognition and synthesis. A memory corruption condition in this component allows an attacker-controlled HTML page to trigger out-of-bounds memory access inside the renderer process.
The issue is scoped to information disclosure rather than code execution. The impact is confined to memory reachable within the Chrome sandbox, which still exposes sensitive data such as page contents from the renderer, origin isolation metadata, and transient state belonging to other browsing contexts hosted in the same process.
Exploitation requires the victim to load an attacker-controlled page. No elevated privileges or prior authentication are required against the browser.
Root Cause
The root cause is classified under [CWE-119], an improper restriction of operations within the bounds of a memory buffer in Chrome's Speech component. A crafted input causes the Speech code path to access memory outside the intended buffer boundaries, returning renderer-process memory to script-reachable surfaces.
Attack Vector
An attacker hosts or injects a crafted HTML page that invokes the Speech API in a manner that triggers the out-of-bounds read. When a user visits the page using a vulnerable Chrome version, the renderer processes the malicious input and leaks sandbox memory contents. The attacker can then exfiltrate recovered bytes through standard script channels. For deeper technical context, see the Chromium Issue Tracker #544498565.
Detection Methods for CVE-2026-113144
Indicators of Compromise
- Chrome renderer processes crashing or exhibiting anomalous memory access patterns after loading untrusted pages that invoke the Web Speech API.
- Outbound network connections from user endpoints to unknown domains immediately following speech-related page interactions.
- Browser telemetry showing versions below 156.0.8078.47 present in the environment after the patch release.
Detection Strategies
- Inventory installed Chrome versions across managed endpoints and flag any build older than 156.0.8078.47.
- Monitor web proxy and DNS logs for user navigation to low-reputation domains that invoke SpeechRecognition or SpeechSynthesis APIs.
- Correlate browser crash reports with recently visited URLs to identify repeated faults within the Speech component.
Monitoring Recommendations
- Enable centralized Chrome crash reporting and ingest events into the SIEM for pattern analysis.
- Track browser version compliance using endpoint management tooling and alert on drift from the patched baseline.
- Monitor for anomalous data exfiltration from browser processes to detect post-exploitation activity.
How to Mitigate CVE-2026-113144
Immediate Actions Required
- Update Google Chrome to version 156.0.8078.47 or later on all managed endpoints.
- Verify Chromium-based browsers downstream of the affected version have incorporated the Speech component fix.
- Restart Chrome after updating to ensure the patched binary is loaded in all renderer processes.
Patch Information
Google released the fix in the Stable channel update documented at the Google Chrome Stable Update advisory. Administrators should push the update through enterprise management tools and confirm deployment via browser version telemetry. Chromium downstream maintainers should pull the corresponding commit referenced in Chromium Issue Tracker #544498565.
Workarounds
- Disable the Web Speech API in enterprise Chrome policies where speech functionality is not required.
- Restrict user navigation to untrusted sites via web filtering or isolation technologies until the patch is deployed.
- Enforce site isolation and strict origin policies to limit the value of memory recoverable from the renderer.
# Verify Chrome version on Linux/macOS endpoints
google-chrome --version
# Windows: query installed version via registry
reg query "HKLM\Software\Google\Update\Clients\{8A69D345-D564-463C-AFF1-A69D9E530F96}" /v pv
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

