EUVD-2026-35205
GHSA-2jmx-42pw-22v9
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
Use after free in Codecs in Google Chrome on Windows 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: High)
AnalysisAI
Sandbox escape in Google Chrome on Windows before 149.0.7827.103 allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a use-after-free in the Codecs component triggered by a crafted HTML page. Google rates this Chromium security severity as High, and a vendor patch is available; no public exploit was identified at time of analysis, though the scope-changed CVSS 8.3 reflects the cross-boundary impact of breaching the 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 (1) the victim to load attacker-controlled HTML in Chrome for Windows prior to 149.0.7827.103 (UI:R - user interaction), and (2) the attacker to already have code execution inside the renderer process, as the description explicitly states 'a remote attacker who had compromised the renderer process' - meaning this CVE alone is not directly exploitable and must be chained with a separate renderer RCE. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H produces 8.3 and accurately captures a multi-stage exploit chain: network reachable, high complexity (race/heap-grooming typical for UAF), no privileges, user must visit a page, and Scope:Changed because the bug crosses the renderer sandbox into the broader browser/OS trust boundary. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first lands a separate renderer-process compromise (for example through a JavaScript engine or DOM bug) when the victim visits a malicious or compromised site in Chrome on Windows. From inside the sandboxed renderer, the attacker delivers a crafted HTML/media payload that triggers the Codecs use-after-free along a code path reachable from the renderer, grooming the heap to gain control of execution and escape into the higher-privileged browser process, achieving code execution outside the sandbox. … |
| Remediation | Vendor-released patch: Chrome 149.0.7827.103 for Windows - upgrade immediately via the Chrome Releases stable channel update at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html, and validate enterprise rollout through Google Update / managed deployment channels. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory all Windows systems running Google Chrome and document current versions. …
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