EUVD-2026-35253
GHSA-5cc5-fjm9-c96q
Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Lifecycle Timeline
4DescriptionNVD
Inappropriate implementation in Extensions in Google Chrome prior to 149.0.7827.103 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Site isolation bypass in Google Chrome Extensions (versions prior to 149.0.7827.103) enables a remote attacker who has already compromised the renderer process to escape cross-origin content boundaries via a crafted HTML page. The vulnerability stems from improper input validation (CWE-20) in the Extensions subsystem, producing a high integrity impact (I:H) with no confidentiality or availability loss per the CVSS vector. …
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 two mandatory preconditions: (1) the attacker must have already achieved code execution within the Chrome renderer process via a separate, independent vulnerability - this is an explicit prerequisite stated in the CVE description, not an inferred condition; and (2) the victim must interact with a crafted HTML page (UI:R per CVSS vector), meaning user-initiated navigation or an existing open tab loaded with attacker-controlled content is necessary. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 6.5 Medium score with vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N warrants careful interpretation against the actual exploitation prerequisites. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who has already gained code execution within a Chrome renderer process - for example, by exploiting a separate memory corruption vulnerability in the browser - then serves the victim a crafted HTML page that triggers the improper input validation flaw in the Extensions subsystem. This causes Chrome to improperly enforce site isolation boundaries, allowing the attacker to write or manipulate content across origins beyond what the compromised renderer should be permitted to access. … |
| Remediation | The primary fix is upgrading Google Chrome to version 149.0.7827.103 or later, which is the vendor-confirmed patched release documented in the Chrome Stable Channel advisory at chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
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