EUVD-2026-35260
GHSA-cqm4-2v9f-324r
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
Insufficient validation of untrusted input in New Tab Page 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: High)
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 Chromium sandbox via a crafted HTML page served through the New Tab Page. Google rates the underlying Chromium severity as High and a fix is shipped in the stable channel, but no public exploit identified at time of analysis and the issue is not listed in CISA KEV.
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 three concrete prerequisites: (1) the attacker must have already compromised the Chrome renderer process - typically via a separate renderer-side RCE delivered through a malicious or attacker-controlled web page; (2) the victim must perform an interaction with the New Tab Page surface (CVSS UI:R), so a fully background drive-by is not in scope; and (3) the target Chrome build must be earlier than 149.0.7827.103 on the desktop stable channel. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 score of 8.3 (AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H) reflects a network-reachable, scope-changing, high-impact bug but with High attack complexity and required user interaction, signalling that exploitation is not turnkey. … 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 site that first triggers a separate renderer-process RCE (a common precondition for modern Chromium sandbox escapes), then serves crafted HTML that abuses the New Tab Page's improperly validated input handling to cross from the sandboxed renderer into the browser process. Once outside the sandbox, the attacker executes code with the browser's privileges on the host, enabling credential theft, persistence, or lateral movement. … |
| Remediation | Vendor-released patch: Chrome 149.0.7827.103 - upgrade all Chrome desktop installations to 149.0.7827.103 or later via the stable channel update described at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html, and force-restart browsers so the new binary actually loads. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Inventory Chrome versions deployed across your organization and assess the scope of exposure. …
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