Skip to main content

Google Chrome EUVDEUVD-2026-65811

| CVE-2026-79275 CRITICAL
Use After Free (CWE-416)
2026-08-25 Chrome GHSA-c8v3-xpmq-f63m
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 page
  2. Delivery
    Deliver malicious WebGL/HTML content
  3. Exploit
    Trigger use-after-free in ANGLE
  4. Execution
    Reclaim freed memory with controlled data
  5. Persist
    Execute code and escape sandbox
  6. Impact
    Compromise host beyond browser

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

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 actively load attacker-controlled HTML/WebGL content in a vulnerable Chrome build below 152.0.7977.65 - the UI:R metric means user interaction (navigating to or opening the crafted page) is mandatory, which is the primary limiting factor. No authentication is required (PR:N, unauthenticated remote attacker) and attack complexity is low (AC:L). The specific technical prerequisite is that the crafted page must exercise the vulnerable ANGLE graphics code path, so environments where WebGL/hardware graphics acceleration is disabled make the vulnerable code harder to reach. There is no dependency on non-default configuration otherwise; standard Chrome installs with default WebGL enabled are exposed.

Impact

The signals are partly divergent and must be weighed together. CVSS 3.1 is 9.6 (Critical) driven by AV:N/AC:L/PR:N with only UI:R and a scope change from sandbox escape - technically a very dangerous, low-complexity, unauthenticated remote bug. SSVC lists Exploitation: none and Automatable: no, but Technical Impact: total, confirming full compromise potential if exploited. EPSS is low at 0.41% (34th percentile), and there is no KEV listing and no public POC, indicating exploitation is not yet occurring or widespread. The reconciling interpretation: this is a high-severity, high-impact vulnerability that is currently NOT under active exploitation, so its real-world priority derives from Chrome's ubiquity and the ease of mass web-based delivery rather than from evidence of in-the-wild use. Because it requires user interaction (visiting a page) and is not automatable per SSVC, it is a strong patch-now candidate but not an emergency zero-day.

Exploit ScenarioDerived

An attacker hosts or compromises a web page containing crafted WebGL/graphics content and entices a victim on a vulnerable Chrome build to visit it (via phishing link, malvertising, or watering hole). Rendering the page triggers the use-after-free in ANGLE, and by grooming freed memory the attacker achieves code execution that escapes the renderer sandbox into a more privileged context. No public exploit is identified at time of analysis, so this reflects capability implied by CVSS AV:N/AC:L/UI:R rather than an observed campaign.

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

Remote code execution in Google Chrome's ANGLE graphics component (versions prior to 152.0.7977.65) lets a remote attacker escape the browser sandbox and run arbitrary code by luring a victim to a crafted HTML page. The flaw is a use-after-free (CWE-416) rated 9.6/Critical with a scope change, meaning exploitation impacts the host beyond the compromised renderer. There is no public exploit identified at time of analysis, and CISA SSVC records exploitation status as none, though the EPSS score of 0.41% reflects only near-term probability, not the true severity of a sandbox-escaping RCE.

RemediationAI

Vendor-released patch: 152.0.7977.65 - upgrade Google Chrome to 152.0.7977.65 or later on all desktop platforms and restart the browser to load the fix, per Google's Chrome Releases advisory (https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html). In managed environments, force the update through enterprise policy and verify the effective version rather than relying on background auto-update, which may lag. As an interim compensating control before patching, you can reduce the ANGLE/WebGL attack surface by disabling hardware acceleration or WebGL (chrome://settings 'Use graphics acceleration when available', or policy) so the vulnerable graphics path is less readily reached - the trade-off is degraded rendering/GPU performance and broken WebGL content. Restricting browsing to trusted sites and enforcing user-interaction awareness reduces the delivery opportunity but does not remove the bug.

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 and OpenGL ES calls onto the platform's native graphics backend (Direct3D, Metal, Vulkan, or desktop GL). Because it processes untrusted GPU/WebGL commands originating from web content, memory-safety bugs here are directly reachable from a web page. The root cause is CWE-416 use-after-free: a memory object is freed but a dangling reference is subsequently used, allowing an attacker to reclaim that memory with controlled data and corrupt program state. Notably the description states code execution occurs 'outside the sandbox,' consistent with ANGLE code paths that run with elevated privilege relative to the renderer, which is why CVSS assigns S:C (scope change). Affected CPE is cpe:2.3:a:google:chrome across all versions below the fixed build.

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

Web-delivered UAF reachable unauthenticated (AV:N/PR:N) with low complexity but requiring the victim to open a page (UI:R); sandbox escape yields S:C and 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:A/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:37 NVD
9.6 (None) 9.6 (CRITICAL)
CVE Published
Aug 25, 2026 - 20:10 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 25, 2026 - 20:10 cve.org
CRITICAL 9.6

DescriptionCVE.org

Use after free in ANGLE in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

Executive ViewAI

Why It Matters

Google Chrome versions prior to 152.0.7977.65 contain a critical use-after-free vulnerability in the ANGLE graphics component enabling remote code execution with sandbox escape. Exploitation requires only that users visit a crafted webpage, allowing attackers to execute arbitrary code on affected systems and potentially access credentials, intellectual property, and sensitive business data stored locally or in browser memory.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 66% exploitable
Prevalence
Ubiquitous
Chrome is among the most widely deployed browsers globally
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

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

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

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

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