EUVD-2026-35219
GHSA-r6r7-44pc-4g42
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in Plugins 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 versions prior to 149.0.7827.103 allows a remote attacker who has already compromised the renderer process to escape cross-origin boundaries via a crafted HTML page. The flaw is rated High severity by Chromium and carries a CVSS score of 8.1, though EPSS is very low at 0.02% and no public exploit identified at time of analysis. …
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 renderer process of Chrome prior to 149.0.7827.103, meaning a separate renderer RCE (e.g., a V8 or Blink bug) must be chained first; this CVE alone is not a standalone entry point. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N produces an 8.1 score driven by network reach, low complexity, and high confidentiality and integrity impact, but the realistic risk is materially lower because the description explicitly requires an attacker to have already compromised the renderer process - a precondition not modeled cleanly in CVSS PR:N. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate renderer-process vulnerability (for example, a V8 type confusion delivered via a malicious ad or compromised website) to achieve code execution inside the sandboxed Chrome renderer. They then load a crafted HTML page that triggers the Plugins origin-validation flaw to reach into or act on behalf of a different origin loaded in the same browser - for example, reading authenticated session data from a banking or webmail tab - without escaping the renderer sandbox entirely. … |
| Remediation | Vendor-released patch: Google Chrome 149.0.7827.103 (desktop stable channel) - update Chrome via the built-in updater and restart the browser to apply, per the Chrome Releases 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 version distribution across endpoints and prepare deployment communications. …
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