EUVD-2026-35229
GHSA-c729-j7cm-x9p7
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Ozone in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)
AnalysisAI
Heap corruption in Google Chrome's Ozone display server component prior to version 149.0.7827.103 allows remote attackers to exploit a use-after-free condition through a malicious web page, with Chromium rating this as Critical severity. Successful exploitation requires the victim to visit attacker-controlled HTML content, but yields high impact on confidentiality, integrity, and availability in the renderer process. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The victim must use Google Chrome at a version below 149.0.7827.103 and must be induced to load attacker-controlled HTML in the browser (UI:R - user interaction required, satisfied by clicking a link, viewing a malicious ad, or being redirected). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.8 score (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a realistic browser-bug profile: network-reachable, low complexity, no authentication, but requires the user to visit a crafted page, and the impact stays inside the renderer sandbox (S:U). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page (or injects it via a compromised ad network or watering-hole site) that uses JavaScript and DOM manipulation to drive Ozone into the vulnerable code path, freeing an object whose dangling pointer is later dereferenced. When a victim running pre-149.0.7827.103 Chrome loads the page, the attacker grooms the heap to place controlled data at the reused allocation, achieving renderer-process code execution that would typically be paired with a separate sandbox-escape bug to compromise the host. … |
| Remediation | Vendor-released patch: update Google Chrome to 149.0.7827.103 or later on all desktop platforms, as published in the Chrome Releases stable-channel advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html); the Chromium tracker entry is https://issues.chromium.org/issues/516674532. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Identify all Google Chrome installations and their versions across all endpoints and identify those prior to 149.0.7827.103. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Vendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today