Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Retained AV:N/PR:N/UI:R per Chromium convention treating renderer compromise as baseline; S:C reflects sandbox escape into the OS with full C/I/A impact, matching 9.6.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
Heap buffer overflow in Color in Google Chrome on ChromeOS prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome on ChromeOS (versions prior to 151.0.7922.72) stems from a heap buffer overflow in the Color component, allowing a remote attacker who has already compromised the renderer process to break out of the sandbox via a crafted HTML page. Chromium rates the severity High and the CVSS score is 9.6 owing to the scope change into the host OS. …
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 | Exploitation requires that the attacker has ALREADY compromised the Chrome renderer process on ChromeOS - this is the explicit precondition stated in the description ('a remote attacker who had compromised the renderer process') and is the primary limiting factor. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H yields 9.6 (Critical), driven by the scope change (S:C) that reflects crossing the sandbox boundary into the OS, with full C/I/A impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first lands a working renderer exploit (e.g., a separate memory-safety bug) when a ChromeOS user visits a malicious website, gaining code execution inside the sandboxed renderer. From that foothold, the attacker delivers crafted HTML/color data that triggers the heap buffer overflow in the Color component to corrupt memory and escape the sandbox, gaining higher-privileged execution on the device. … |
| Remediation | Vendor-released patch: 151.0.7922.72 - upgrade Google Chrome/ChromeOS to 151.0.7922.72 or later, as published in the Chrome Stable Channel update advisory (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit your ChromeOS fleet to identify current Chrome versions and prioritize devices with auto-update disabled. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-122 – Heap-based Buffer Overflow
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-50806
GHSA-cwp6-3cc4-8qxc