Google Chrome up to 151.0.7922.173 ANGLE uninitialized resource

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.1$5k-$25k0.63+

Summaryinfo

A vulnerability marked as problematic has been reported in Google Chrome. Affected is an unknown function of the component ANGLE. This manipulation causes uninitialized resource. This vulnerability is handled as CVE-2026-79229. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability has been found in Google Chrome and classified as problematic. Affected by this vulnerability is an unknown code of the component ANGLE. The manipulation with an unknown input leads to a uninitialized resource vulnerability. The CWE definition for the vulnerability is CWE-908. The product uses or accesses a resource that has not been initialized. As an impact it is known to affect confidentiality. The summary by CVE is:

Uninitialized resource in ANGLE in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

The advisory is shared at chromereleases.googleblog.com. This vulnerability is known as CVE-2026-79229 since 08/25/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/26/2026).

Upgrading to version 152.0.7977.65 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 4.1

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Uninitialized resource
CWE: CWE-908
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Chrome 152.0.7977.65

Timelineinfo

08/25/2026 CVE reserved
08/26/2026 +1 days Advisory disclosed
08/26/2026 +0 days VulDB entry created
08/26/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: google.com
Product: google.com

Advisory: chromereleases.googleblog.com
Status: Confirmed

CVE: CVE-2026-79229 (🔒)
GCVE (CVE): GCVE-0-2026-79229
GCVE (VulDB): GCVE-100-395581

Entryinfo

Created: 08/26/2026 02:46
Changes: 08/26/2026 02:46 (56)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!