EUVD-2026-35226
GHSA-gpxh-m862-v6vq
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
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 Tracing 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: Medium)
AnalysisAI
Sandbox escape in Google Chrome prior to 149.0.7827.103 allows a remote attacker who has already compromised the renderer process to break out of the sandbox via a use-after-free flaw in the Tracing component, triggered through a crafted HTML page. No public exploit identified at time of analysis, and SSVC indicates exploitation status is 'none', but the technical impact is rated total because a successful escape grants code execution at browser-process privileges. …
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 - this is explicitly stated in the CVE description and is the gating prerequisite, meaning the bug is a sandbox-escape primitive rather than a standalone remote vulnerability. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals here are mixed and point to a serious-but-not-emergency issue. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A targeted user visits an attacker-controlled or compromised website and is induced to interact with it (the UI:R requirement), which first triggers a separate renderer-side RCE to gain code execution inside the sandboxed renderer. The attacker's renderer-side payload then sends crafted IPC messages to the browser process's Tracing component, triggering the use-after-free to corrupt memory and pivot execution into the browser process, escaping the sandbox and gaining the user's privileges on the host. … |
| Remediation | Update Google Chrome to version 149.0.7827.103 or later on Windows, macOS, and Linux via the stable-channel update described at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html - this is the vendor-released patch and the primary fix. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
24 hours: Alert stakeholders, identify Chrome deployment scope, verify patch availability in your environment. …
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