EUVD-2026-35240
GHSA-p626-pw8w-29p4
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Integer overflow in libyuv in Google Chrome prior to 149.0.7827.103 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)
AnalysisAI
Sandbox escape in Google Chrome versions prior to 149.0.7827.103 enables a remote attacker who has already compromised the renderer process to break out of the browser sandbox via an integer overflow in the libyuv image conversion library. Exploitation requires user interaction with a crafted HTML page and a chained renderer compromise, but Google rated the underlying issue Critical because a successful chain yields code execution outside Chrome's sandbox. …
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 the attacker to have already compromised Chrome's renderer process - this bug is a sandbox-escape primitive, not a primary RCE - and the target user must visit (UI:R) a crafted HTML page that delivers attacker-controlled inputs to libyuv conversion routines. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.3 vector (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) correctly reflects that the bug is reachable over the network, requires high attack complexity, requires user interaction (visiting a page), and crosses a scope boundary (the sandbox) when exploited - all hallmarks of a sandbox-escape primitive that is only useful as the second stage of an exploit chain. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker lures a target to a malicious or compromised website that first triggers a separate renderer-process vulnerability to achieve code execution inside the sandboxed renderer, then serves crafted image or video data that drives libyuv into the integer overflow, corrupting memory at a sandbox boundary and pivoting to code execution in a more privileged Chrome process. Because no public exploit has been identified and attack complexity is rated High, this is most plausible as the second stage of a targeted exploit chain rather than commodity drive-by malware. |
| Remediation | Vendor-released patch: Google Chrome 149.0.7827.103 - update Chrome to 149.0.7827.103 or later via the stable channel and restart the browser to apply, as described at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html (tracking issue https://issues.chromium.org/issues/517339758). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
24 hours: Identify all systems running Chrome versions prior to 149.0.7827.103 using endpoint management or vulnerability scanning tools. …
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