Google Chrome Security Update: 11 Critical CVEs Disclosed in November 2026
Google Chrome's November 2026 security update addresses 11 critical-scored CVEs affecting ANGLE, GPU, WebGL, Tint, and other browser components. Explore the vulnerabilities, potential sandbox escapes, affected versions, security risks, and mitigation steps.
Google Chrome Security Update: 11 Critical CVSS Vulnerabilities Disclosed in November 2026
Summary
Google released a major security update for Google Chrome on November 17, 2026, addressing 204 security issues across several browser components. Among the published vulnerabilities, this analysis focuses on 11 CVEs assigned a CVSS v3.1 base score of 9.6 (Critical), affecting ANGLE, GPU, WebGL, Tint, Color, and WebAppInstalls.
These vulnerabilities include out-of-bounds memory writes, out-of-bounds reads, use-after-free conditions, buffer overflows, improper input validation, and protection mechanism failures. Several published vulnerability descriptions identify the potential for arbitrary code execution outside Chrome's sandbox through specially crafted HTML pages.
Exploitation of these weaknesses could undermine browser process isolation, compromise memory integrity, and potentially allow attacker-controlled code to execute beyond the restrictions normally applied to untrusted web content. The actual exploitation requirements differ between CVEs, and some vulnerabilities specifically affect Google Chrome for Android or require an already compromised renderer process.
Severity classification: The 11 vulnerabilities covered in this article are selected based on their CVSS v3.1 score of 9.6 (Critical). Google's Chromium security ratings are separate and vary between Critical, High, Medium, and Low. These classifications should not be treated as equivalent.
Scope: This article covers the 11 selected CVSS-Critical vulnerabilities and does not represent every vulnerability rated Critical by Google in the same release. Four additional Google-rated Critical vulnerabilities are identified separately below to provide a complete picture of the vendor's highest-priority findings.
Security update: Google released Chrome 158.0.8127.36 for Linux, 158.0.8127.36/.37 for Windows and macOS, and 158.0.8127.42 for Android on November 17, 2026. Organizations should deploy these or later patched releases appropriate to their platforms.
Google's official announcements are available through the Chrome Releases - November 2026 publication archive.
Vulnerability Details
The following 11 CVEs carry a CVSS v3.1 base score of 9.6 (Critical) in the published vulnerability records used for this analysis. The table separately identifies the Chromium security severity assigned by Google.
| CVE ID | CVSS v3.1 | Google Severity | Vulnerability Type | Component |
|---|---|---|---|---|
| CVE-2026-130910 | 9.6 Critical | High | Protection mechanism failure | ANGLE (Android) |
| CVE-2026-130971 | 9.6 Critical | Medium | Out-of-bounds write | ANGLE |
| CVE-2026-130994 | 9.6 Critical | High | Use-after-free | WebGL |
| CVE-2026-130996 | 9.6 Critical | High | Out-of-bounds write | ANGLE |
| CVE-2026-131025 | 9.6 Critical | High | Out-of-bounds read | ANGLE |
| CVE-2026-131031 | 9.6 Critical | Critical | Out-of-bounds write | GPU |
| CVE-2026-131054 | 9.6 Critical | Critical | Out-of-bounds write | ANGLE |
| CVE-2026-131057 | 9.6 Critical | High | Out-of-bounds read | ANGLE (Android) |
| CVE-2026-131061 | 9.6 Critical | Medium | Buffer overflow | Color |
| CVE-2026-131077 | 9.6 Critical | Medium | Out-of-bounds write | Tint |
| CVE-2026-131088 | 9.6 Critical | Low | Improper input validation | WebAppInstalls |
Important: CVSS v3.1 measures vulnerability severity using a standardized scoring framework, whereas Chromium security severity reflects Google's assessment of the vulnerability within its product and exploitation context. A CVE carrying a Critical CVSS score may therefore have a lower Chromium severity rating, particularly when exploitation requires additional conditions.
Additional Vulnerabilities Rated Critical by Google
Google's November 17, 2026 Chrome security announcement also identifies four additional vulnerabilities with a Critical Chromium severity rating that are not included in the selected group of 11 CVEs. These issues are listed separately to prevent confusion between the article's CVSS-based selection and Google's vendor severity ratings.
| CVE ID | Google Severity | Vulnerability Type | Component |
|---|---|---|---|
| CVE-2026-130963 | Critical | Use-after-free | WebView |
| CVE-2026-131060 | Critical | Buffer overflow | Media |
| CVE-2026-131008 | Critical | Use-after-free | GarbageCollection |
| CVE-2026-130975 | Critical | Use-after-free | WebAudio |
These four vulnerabilities warrant independent remediation prioritization because Google rates them Critical. They are not included in the detailed technical analysis below, which remains focused on the original 11 CVSS-Critical CVEs. The same November 17 Chrome security release provides the corresponding fixes for affected installations.
Technical Information
CVE-2026-130910 - Protection Mechanism Failure in ANGLE
CVE-2026-130910 is a protection mechanism failure affecting ANGLE in Google Chrome for Android. ANGLE is a graphics translation layer used by Chromium to translate graphics operations across different rendering APIs and hardware platforms.
The vulnerability concerns a failure in a security protection associated with graphics processing. An attacker may construct a specially crafted HTML page that reaches the vulnerable ANGLE functionality and causes the intended security boundary to be bypassed.
According to the published CVE description, a remote attacker could potentially execute arbitrary code outside Chrome's sandbox on affected Android installations. The vulnerability is classified as CVSS v3.1 9.6 Critical, while Google assigns a High Chromium security severity.
Platform applicability: Google Chrome for Android. This vulnerability should not be assumed to affect desktop Chrome installations without separate evidence.
CVE-2026-130971 - Out-of-Bounds Write in ANGLE
CVE-2026-130971 is an out-of-bounds write vulnerability affecting ANGLE. This type of memory safety weakness occurs when software writes data beyond the boundaries of an allocated memory region or object.
The vulnerability may be triggered when specially crafted HTML content reaches the affected graphics-processing functionality. An invalid memory write can corrupt neighboring memory objects, modify internal application state, or interfere with subsequent program execution.
The published vulnerability description identifies potential arbitrary code execution outside Chrome's sandbox as a possible security consequence. Practical exploitation depends on the affected memory allocation, the operating environment, and applicable browser protections.
Google rates the vulnerability Medium under Chromium's security classification, despite its Critical CVSS v3.1 score.
CVE-2026-130994 - Use-After-Free Vulnerability in WebGL
CVE-2026-130994 is a use-after-free vulnerability affecting WebGL, the browser technology that enables hardware-accelerated two-dimensional and three-dimensional graphics rendering within web applications.
A use-after-free condition occurs when software attempts to access memory after the corresponding object has been released. If that memory has subsequently been allocated to another object, the stale reference may access or modify data belonging to an unintended memory structure.
An attacker may use a specially crafted HTML page to reach the vulnerable WebGL processing path. Depending on the resulting memory conditions, successful exploitation could result in memory corruption and potentially arbitrary code execution outside the sandbox.
Google's Chromium severity classification for this issue is High.
CVE-2026-130996 - Memory Corruption Through Out-of-Bounds Write in ANGLE
CVE-2026-130996 involves an out-of-bounds write in ANGLE. The weakness affects memory operations associated with Chrome's graphics processing and translation environment.
When crafted web content reaches the affected processing path, a memory operation may write beyond the intended allocation. This can damage neighboring memory structures and potentially influence the execution state of the affected process.
The CVE description identifies potential arbitrary code execution outside the browser sandbox. The precise exploitation method depends on the vulnerable code path and applicable mitigations.
Google assigns a High Chromium severity rating, while the published CVSS v3.1 score is 9.6 Critical.
CVE-2026-131025 - Out-of-Bounds Read in ANGLE
CVE-2026-131025 is an out-of-bounds read vulnerability affecting ANGLE. An out-of-bounds read occurs when software accesses memory outside the valid range of an allocated buffer or object.
The flaw may be reached through graphics-related processing involving specially crafted web content. An invalid read can access unintended memory, cause abnormal application behavior, or expose information about the process memory layout.
Such information can be valuable in memory exploitation scenarios, although an out-of-bounds read does not automatically provide arbitrary code execution. The published CVE description identifies potential execution outside Chrome's sandbox, subject to the affected implementation and exploitation requirements.
The vulnerability carries a High Chromium security severity rating.
CVE-2026-131031 - Critical Out-of-Bounds Write in Chrome GPU
CVE-2026-131031 is an out-of-bounds write vulnerability affecting Google Chrome's GPU component. The GPU subsystem processes graphics operations used for rendering, compositing, and hardware-accelerated browser functionality.
The flaw can potentially be triggered when specially crafted web content causes the affected GPU processing functionality to perform an invalid memory write. Depending on the affected memory structures, corruption may alter internal process state or interfere with execution control.
Google rates this vulnerability Critical, and the published CVSS v3.1 score is also 9.6 Critical. The reported potential for arbitrary code execution outside the sandbox makes the issue significant for enterprise browser security.
CVE-2026-131054 - Critical Out-of-Bounds Write in ANGLE
CVE-2026-131054 is an out-of-bounds write vulnerability affecting ANGLE. The issue involves insufficient memory boundary enforcement within Chrome's graphics translation layer.
An attacker may construct a specially crafted HTML page that exercises the vulnerable graphics functionality. The resulting memory operation may write beyond an allocated region, corrupting neighboring application memory.
The vulnerability description identifies arbitrary code execution outside Chrome's sandbox as a potential result. Google classifies the issue as Critical, making it one of the highest-priority vulnerabilities in the November 17 release.
The vulnerability also carries a CVSS v3.1 score of 9.6 Critical.
CVE-2026-131057 - Out-of-Bounds Read in ANGLE on Android
CVE-2026-131057 is an out-of-bounds read vulnerability affecting Google Chrome for Android. The flaw exists in ANGLE, the graphics translation layer used by Chromium to process graphics operations across supported rendering backends.
An attacker may use a specially crafted HTML page to reach the vulnerable ANGLE processing path on an affected Android device. The flaw may cause the component to read memory outside the intended bounds of an allocated object.
Depending on the affected memory region, the invalid read may cause abnormal behavior, expose unintended memory data, or contribute to more complex exploitation conditions.
The published vulnerability description identifies potential arbitrary code execution outside the browser sandbox. The vulnerability carries a CVSS v3.1 score of 9.6 Critical, while Google's Chromium severity is High.
Platform applicability: Google Chrome for Android. The Android-specific scope should be considered during vulnerability assessment and patch prioritization. Desktop Chrome should not be classified as affected by this CVE solely because it uses ANGLE.
CVE-2026-131061 - Buffer Overflow in Chrome Color Component
CVE-2026-131061 is a buffer overflow vulnerability affecting Chrome's Color component, which participates in processing color-related information required for rendering web content.
A buffer overflow occurs when software processes or writes more data than the destination buffer can safely accommodate. Depending on the memory allocation involved, such an overflow may corrupt adjacent objects or disrupt program execution.
The vulnerability description identifies crafted HTML content as a possible attack delivery mechanism and arbitrary code execution outside the browser sandbox as a potential consequence.
Google assigns a Medium Chromium severity rating, while the CVSS v3.1 score is 9.6 Critical.
CVE-2026-131077 - Out-of-Bounds Write in Tint Shader Processing
CVE-2026-131077 is an out-of-bounds write vulnerability affecting Tint, a shader-processing component used within Chromium's graphics infrastructure.
Tint processes shader representations used by browser graphics functionality. Improper memory boundary handling during such operations may cause data to be written outside an allocated buffer.
A maliciously crafted HTML page may reach the affected processing path and trigger memory corruption. The published description identifies potential arbitrary code execution outside Chrome's sandbox.
The CVE carries a CVSS v3.1 score of 9.6 Critical, while Google rates the issue Medium.
CVE-2026-131088 - Improper Input Validation in WebAppInstalls
CVE-2026-131088 is an improper input validation vulnerability affecting WebAppInstalls, a component associated with installing web applications through Google Chrome.
Unlike vulnerabilities that may be triggered directly through malicious web content, the published description explicitly requires an attacker who has already compromised the renderer process.
After achieving that prerequisite, an attacker may potentially abuse insufficient input validation within WebAppInstalls to execute arbitrary code outside Chrome's sandbox.
This makes the issue relevant to potential browser exploit chaining rather than a standalone compromise without prior access to the renderer process.
The vulnerability carries a CVSS v3.1 score of 9.6 Critical, but Google assigns a Low Chromium security severity.
Affected Products
Google Chrome
The 11 selected vulnerabilities affect components involved in graphics processing, GPU operations, shader translation, memory handling, and web application installation. The affected platform and exploitation prerequisites differ by CVE.
- ANGLE: CVE-2026-130910, CVE-2026-130971, CVE-2026-130996, CVE-2026-131025, CVE-2026-131054, and CVE-2026-131057.
- GPU: CVE-2026-131031.
- WebGL: CVE-2026-130994.
- Color: CVE-2026-131061.
- Tint: CVE-2026-131077.
- WebAppInstalls: CVE-2026-131088.
Android-specific vulnerabilities: CVE-2026-130910 and CVE-2026-131057 specifically identify Google Chrome for Android in their published descriptions.
Desktop vulnerability assessment should therefore distinguish these Android-specific issues from vulnerabilities affecting the general Chrome codebase.
Other Chromium-based applications may include related vulnerable code, but their applicability and fixed versions must be verified through the corresponding vendor advisories.
Affected and Fixed Versions
Google published platform-specific Chrome 158 security releases on November 17, 2026. The releases address the vulnerabilities discussed in this article, subject to individual platform applicability.
| Platform | Affected Versions | Fixed Version |
|---|---|---|
| Google Chrome - Linux | Applicable vulnerable versions prior to 158.0.8127.36 | 158.0.8127.36 or later patched release |
| Google Chrome - Windows | Applicable vulnerable versions prior to the fixed Chrome 158 build | 158.0.8127.36/.37 or later patched release |
| Google Chrome - macOS | Applicable vulnerable versions prior to the fixed Chrome 158 build | 158.0.8127.36/.37 or later patched release |
| Google Chrome - Android | Applicable vulnerable versions prior to the fixed Android release | 158.0.8127.42 or later patched release |
Google's Android release announcement states that Android builds contain the same security fixes as their corresponding desktop releases unless otherwise noted.
The Linux release uses
158.0.8127.36,
Windows and macOS use
158.0.8127.36/.37,
and the Android release
uses 158.0.8127.42.
These are the versions
announced on November 17,
rather than a claim
that they remain the
newest available builds.
Organizations should install the latest patched release available for each operating system and verify the installed version after restarting Chrome.
For the official platform-specific release announcements, see Google Chrome Releases, November 2026 .
Impact
The combined security impact of these vulnerabilities is concentrated around memory safety, browser process isolation, and the potential execution of attacker-controlled code outside Chrome's sandbox.
The following consequences summarize the primary security and business risks without repeating the individual technical vulnerability descriptions.
- Browser Sandbox Compromise: Several vulnerabilities describe the possibility of arbitrary code execution outside Chrome's sandbox, potentially undermining protections that isolate untrusted web content.
- Memory Integrity Risks: Out-of-bounds writes, buffer overflows, and use-after-free weaknesses may corrupt memory used by the browser or its supporting components.
- Potential Information Exposure: Out-of-bounds read vulnerabilities may expose unintended memory contents, depending on the affected implementation and exploitation conditions.
- Endpoint Compromise: Successful exploitation outside the browser sandbox may provide an attacker with capabilities beyond those normally available to untrusted web content. The precise level of access depends on the operating system and additional security restrictions.
- Android Exposure: CVE-2026-130910 and CVE-2026-131057 specifically affect Google Chrome for Android, making mobile browser updates an important part of the remediation process.
- Vulnerability Chaining: CVE-2026-131088 requires an already compromised renderer process, illustrating how a vulnerability may become significant when combined with a separate initial compromise.
- Enterprise Exposure: Outdated Chrome installations on managed endpoints, administrator workstations, and systems used to access untrusted websites may increase an organization's attack surface and remediation workload.
Exploitation status: The potential outcomes described above are based on vulnerability characteristics and published security descriptions. They do not establish that the selected CVEs have been successfully exploited in a verified real-world attack.
MITRE ATT&CK Mapping
The following MITRE ATT&CK mapping identifies techniques that may be relevant to browser vulnerability exploitation. The mappings are hypothetical and should not be interpreted as confirmed attacker activity involving these specific CVEs.
T1189 and T1203 are included as possible techniques associated with malicious websites and client-side exploitation. Other tactics are marked N/A because the reviewed disclosures do not establish related attacker behavior.
| Tactic | Technique ID | Technique Name | Context |
|---|---|---|---|
| Reconnaissance | N/A | N/A | No specific attacker reconnaissance activity established. |
| Resource Development | N/A | N/A | No attacker infrastructure or resource preparation confirmed. |
| Initial Access | T1189 | Drive-by Compromise | Possible delivery through a malicious or compromised website containing specially crafted browser content. Not an observed attack. |
| Execution | T1203 | Exploitation for Client Execution | Possible exploitation of vulnerable Chrome components to execute attacker-controlled code in a client environment. Not an observed attack. |
| Persistence | N/A | N/A | No persistence mechanism or campaign behavior established. |
| Privilege Escalation | N/A | N/A | Potential sandbox boundary crossing does not independently establish a specific observed privilege escalation technique. |
| Stealth | N/A | N/A | No evidence of exploitation intended to conceal activity or suppress logging. T1211, Exploitation for Stealth, is therefore not assigned. |
| Defense Impairment | N/A | N/A | No confirmed disabling or impairment of security tools. |
| Credential Access | N/A | N/A | No credential theft activity established. |
| Discovery | N/A | N/A | No observed system or network discovery activity. |
| Lateral Movement | N/A | N/A | No lateral movement technique established. |
| Collection | N/A | N/A | No observed information collection activity. |
| Command and Control | N/A | N/A | No command-and-control infrastructure or communication technique identified. |
| Exfiltration | N/A | N/A | No confirmed exfiltration activity. |
| Impact | N/A | N/A | No observed campaign-specific impact technique. |
MITRE classification note: MITRE ATT&CK currently identifies T1211 as Exploitation for Stealth under the Stealth tactic. A browser sandbox escape does not automatically satisfy that technique. It has therefore been excluded from the active mappings above.
Mitigation and Recommendations
Priority recommendation: Install the latest patched Google Chrome release appropriate to each operating system. The November 17, 2026 security releases provide fixes in 158.0.8127.36 for Linux, 158.0.8127.36/.37 for Windows and macOS, and 158.0.8127.42 for Android. Restart Chrome after updating and verify the installed version.
Update Google Chrome
On Windows, macOS, and Linux, open Google Chrome and navigate to:
chrome://settings/help
Chrome will check for available updates. Install the latest supported stable release and restart the browser when prompted.
On Android, open Google Play, locate Google Chrome, and install the available patched update. Verify the application version after installation.
Verify the Installed Version
Windows: Use PowerShell to inspect the installed Google Chrome executable:
(Get-Item "C:\Program Files\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion
Linux: Check the version reported by the installed Chrome executable:
google-chrome --version
macOS: Check the version of the installed Google Chrome application:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version
Additional Security Recommendations
- Prioritize browser updates: Identify Google Chrome installations that have not received the applicable fixed release and schedule remediation according to their exposure and business criticality.
-
Include Android devices:
Ensure Google Chrome
for Android is updated
to version
158.0.8127.42or a later patched release, particularly for CVE-2026-130910 and CVE-2026-131057. - Maintain browser sandboxing: Keep Chrome's built-in security protections, sandboxing, and site isolation features enabled wherever supported.
- Restrict untrusted content: Reduce unnecessary exposure to suspicious websites and links, especially on systems that have not yet received the updates.
- Monitor suspicious activity: Investigate abnormal Chrome crashes, unexpected child processes, and unauthorized executable launches associated with browser activity.
- Control browser extensions: Restrict unnecessary extensions and enforce approved extension policies across managed endpoints.
- Review Chromium-based products: Assess browsers and applications that embed Chromium independently and apply the relevant vendor security updates.
- Validate remediation: Reassess managed endpoints after patch installation to confirm that vulnerable Chrome versions are no longer present.
- Track vendor advisories: Monitor Google's official November 2026 Chrome release announcements for additional security information and subsequent patched releases.
Applying the appropriate Chrome security update, maintaining browser security controls, and validating endpoint patch status provide the most direct means of reducing exposure to the vulnerabilities covered in this article.
Instantly Fix Risks in Endpoints & Cloud with Saner
Saner is a continuous and integrated vulnerability & exposure management platform that instantly fixes risks in endpoints and cloud.




