Skip to main content

Google Chrome CVE-2026-78989

| EUVDEUVD-2026-65762 CRITICAL
Out-of-bounds Read (CWE-125)
2026-08-25 Chrome GHSA-w6fp-j497-w2rr
9.6
CVSS 3.1 · Vendor: Chrome
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure victim to crafted HTML page
  2. Delivery
    Page invokes vulnerable ANGLE/WebGL rendering
  3. Exploit
    Trigger out-of-bounds read in ANGLE
  4. Execution
    Leak memory and corrupt state
  5. Persist
    Escape renderer sandbox
  6. Impact
    Execute arbitrary code on host

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK

1 technique across 1 tactic: Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the victim to load attacker-controlled HTML in a vulnerable Chrome build (before 152.0.7977.65) on Windows - user interaction is mandatory (UI:R), so the attacker must lure the user to a crafted page rather than trigger it silently. The flaw is in the Windows ANGLE-to-Direct3D graphics path, making it platform-specific to Windows; non-Windows Chrome is not indicated as affected. No authentication or prior privileges are needed (PR:N). Limiting factors: required user interaction, dependence on the browser exercising the vulnerable graphics code (WebGL/GPU rendering), and the technical difficulty of turning an out-of-bounds read into a reliable sandbox escape and code execution.

Impact

Signals conflict in an instructive way. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H = 9.6) is severe because it combines network reach, low complexity, no privileges, and a scope change reflecting sandbox escape - only user interaction (visiting a page) is required. Against that, EPSS is only 0.42% (35th percentile), there is no CISA KEV listing, and no public exploit is identified, indicating that despite the high CVSS this is not currently under active or widespread exploitation. Browser bugs of this class are high-value but typically require chaining and reliable heap grooming, so weaponization is non-trivial. Net: a genuine high-priority patch item for any Windows Chrome fleet given ubiquity and sandbox-escape potential, but not an emergency 'exploited-now' scenario based on the available data.

Exploit ScenarioDerived

An attacker hosts or injects a malicious HTML page containing crafted WebGL/graphics content that triggers the out-of-bounds read in ANGLE when rendered. A victim running vulnerable Chrome on Windows visits the page (e.g., via phishing link or malvertising), and the attacker leverages the resulting memory disclosure and corruption to attempt code execution outside the renderer sandbox. No public exploit is identified at time of analysis, so this remains a plausible but unproven chain.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 26, 2026

Out-of-bounds read in Chrome's ANGLE graphics component (Windows builds prior to 152.0.7977.65) lets a remote attacker escape the renderer sandbox and potentially run arbitrary code after a victim opens a crafted HTML page. Google rates the Chromium severity High, and the CVSS is 9.6 driven by the sandbox-escape scope change; there is no public exploit identified at time of analysis and EPSS is low (0.42%).

RemediationAI

Vendor-released patch: update Google Chrome to 152.0.7977.65 or later on Windows via the Stable channel (https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html) and restart the browser, since Chrome updates only take effect after a relaunch. For managed fleets, push the update through enterprise policy / update management and verify the running build. As an interim compensating control before patching, disabling hardware acceleration in Chrome (chrome://settings, 'Use graphics acceleration when available') routes rendering away from the ANGLE/GPU path - trade-off is degraded rendering/video performance and it is not a guaranteed mitigation. Restricting users to trusted sites reduces exposure to the crafted-page delivery vector but does not eliminate risk.

Affected VersionsENISA

Chrome 152.0.7977.65 <152.0.7977.65

Affected Packages

euvd chrome fix: 152.0.7977.65

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

ANGLE (Almost Native Graphics Layer Engine) is Chrome's graphics abstraction layer that translates WebGL / OpenGL ES calls into the platform's native API - on Windows this is Direct3D. Because ANGLE bridges untrusted web content to the GPU stack at a privileged layer, a memory-safety defect here can cross the renderer sandbox boundary. The root cause is CWE-125 (Out-of-bounds Read): the component reads memory outside the bounds of an allocated buffer, which can leak adjacent memory and, combined with other primitives, corrupt state sufficient to gain code execution. The CPE cpe:2.3:a:google:chrome confirms the Chrome application itself as the affected product, with the flaw specific to the Windows platform per the advisory.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Chrome) PRIMARY 9.6 CRITICAL
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
vuln.today AI 9.6 CRITICAL

Remote crafted page needs only a victim visit (UI:R, PR:N, AC:L); sandbox escape justifies scope change (S:C) with full C/I/A impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
SUSE CRITICAL
Red Hat 9.6 CRITICAL

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Aug 26, 2026 - 16:22 NVD
9.6 (CRITICAL)
CVE Published
Aug 25, 2026 - 20:09 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 25, 2026 - 20:09 cve.org
CRITICAL 9.6

DescriptionCVE.org

Out of bounds read in ANGLE in Google Chrome on on Windows prior to 152.0.7977.65 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

Executive ViewAI

Why It Matters

A critical sandbox-escape vulnerability in Google Chrome's graphics engine (CVE-2026-78989, CVSS 9.6) affects Windows users on versions prior to 152.0.7977.65, allowing arbitrary code execution after a user opens a crafted web page. Organizations with Windows Chrome deployments must prioritize remediation due to the high severity and potential for immediate system compromise.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 65% exploitable
Prevalence
Ubiquitous
Chrome is among the most widely deployed browsers on Windows endpoints
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +48
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Package Hub 15 SP7 Fixed
openSUSE Leap 16.0 Fixed
openSUSE Tumbleweed Fixed
SUSE Package Hub 15 SP7 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy