Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Insufficient validation of untrusted input in UI in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome prior to 149.0.7827.103 allows a remote attacker to break out of the browser's renderer sandbox via a crafted HTML page that exploits insufficient input validation in the UI layer. The scope-changing CVSS 9.6 reflects that successful exploitation crosses the sandbox security boundary, though user interaction (visiting a malicious page) is required. …
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 be running a vulnerable Chrome build (any version below 149.0.7827.103) and must actively load attacker-controlled HTML content in the browser - per CVSS UI:R, exploitation cannot occur without that user action, but no authentication, special browser configuration, extension, or non-default flag is required, and the malicious page can be delivered via any normal web channel (link click, iframe, ad, redirect). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 9.6 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H) indicates network-reachable, low-complexity, unauthenticated exploitation with full confidentiality, integrity, and availability impact across a security boundary - only user interaction (visiting a page) gates it, which is trivially achievable via phishing, malvertising, or watering-hole attacks. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts or injects a crafted HTML page (e.g., via phishing email, malicious ad network, or compromised site) and lures a Chrome user to visit it; when the page is rendered, the malformed input triggers the UI validation flaw and escapes the renderer sandbox, giving the attacker code execution at the browser-process privilege level on the victim's host. From there the attacker can read cross-origin data, persist on the endpoint, or chain to OS-level privilege escalation. … |
| Remediation | Upgrade Google Chrome to version 149.0.7827.103 or later on all desktop platforms; this is the vendor-released patch identified in the Chrome Releases stable-channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Audit Chrome deployment across your environment and prepare patch deployment to version 149.0.7827.103 or later. …
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
EUVD-2026-35223
GHSA-rxx6-vjpq-6755