Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitTrigger SiteIsolation authorization bypass
-
ExecutionBreak cross-site process boundary
-
ImpactExecute arbitrary code in browser context
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to use a Chrome build prior to 155.0.8059.39 and to visit attacker-controlled or compromised web content containing a crafted HTML page that triggers the SiteIsolation incorrect-authorization condition (CWE-863). No authentication or prior privileges are needed (PR:N), but the required user interaction (UI:R) - navigating to the malicious page - is the primary limiting factor and is why SSVC rates the flaw non-automatable. There is no indication of a non-default configuration dependency; standard Chrome with SiteIsolation enabled (the default) is the target. Realistic risk is bounded by the need for social-engineering/drive-by delivery rather than unattended remote compromise. |
| Impact | Signals are mixed and should be weighed carefully. The CVSS 3.1 base score of 9.6 is driven by network attack vector (AV:N), low complexity (AC:L), no privileges required (PR:N), and a changed scope (S:C) with total CIA impact - consistent with a SiteIsolation authorization bypass that breaks Chrome's cross-origin security boundary and yields arbitrary code execution. However, the attack requires user interaction (UI:R): a victim must visit a crafted HTML page, which meaningfully lowers the practical severity versus a zero-click flaw. The SSVC framework tempers the picture further: Exploitation is rated 'none' (no observed or public exploitation), Automatable is 'no' (user interaction prevents mass/wormable automation), while Technical Impact is 'total' - so the capability ceiling is high but the likelihood of broad exploitation is currently low. There is no KEV listing and no POC reported in the provided data, so this is not confirmed active exploitation. No EPSS score was supplied, so probabilistic exploitation likelihood cannot be quantified here. Net assessment: this is a genuinely high-impact browser flaw in a ubiquitous product and warrants prompt patching, but the current real-world risk is 'patch promptly' rather than 'emergency/exploited-in-wild,' given required user interaction, non-automatable exploitation, and no evidence of active abuse. |
| Exploit ScenarioDerived | A remote attacker hosts or compromises a web page containing crafted HTML that abuses the SiteIsolation incorrect-authorization flaw; when a victim using a vulnerable Chrome build (prior to 155.0.8059.39) visits the page, the attacker bypasses cross-site process isolation and executes arbitrary code in the victim's browser context. No authentication is required (PR:N) but the victim must be lured into visiting the page (UI:R). No public exploit code was identified in the provided data at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 07, 2026
Incorrect authorization (CWE-863) in Google Chrome's SiteIsolation component allows an unauthenticated remote attacker to execute arbitrary code in the browser when a victim loads a crafted HTML page, a flaw Google rates High and that carries a CVSS base score of 9.6. Exploitation is limited by the required user interaction (UI:R) - the victim must visit attacker-controlled or compromised web content on a build older than 155.0.8059.39 - so delivery hinges on drive-by browsing or social engineering rather than unattended compromise, consistent with CISA's SSVC rating of non-automatable. No public exploit code has been identified at time of analysis, and a vendor-released patch is available in Chrome 155.0.8059.39.
RemediationAI
Vendor-released patch: Chrome 155.0.8059.39. Update Google Chrome to that version or later via the stable channel release (https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_086471744.html) and fully restart the browser so the new binary is loaded. No documented configuration workaround exists, and disabling Site Isolation is not a valid mitigation - that feature is itself the security boundary the flaw abuses, so turning it off would remove the protection entirely and expose the browser to other cross-origin bugs. Until all endpoints are updated, administrators should enforce the minimum version through Chrome Browser Cloud Management or their update/MDM policies, verify the installed build at chrome://version, and, for high-risk user groups, temporarily restrict browsing to allowlisted trusted sites via web proxy - accepting the obvious productivity cost - to shrink the drive-by attack surface. Because exploitation requires user interaction, reinforcing phishing and malicious-link awareness remains relevant during the patch window; no public exploit code was identified at time of analysis.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
SiteIsolation is Chrome's process-per-site architecture: it places content from different sites in separate renderer processes so the same-origin policy is enforced by the browser, not by the renderer, containing the damage a compromised page can cause. CVE-2026-102322 is an instance of CWE-863 (Incorrect Authorization), meaning an authorization check inside that isolation logic returns the wrong decision, so a crafted HTML page can obtain renderer capabilities or reach data it should not be granted, escalating to arbitrary code execution. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H describes a network-reachable, unauthenticated attack that still requires the victim to load the page; the S:C (scope changed) metric confirms the impact crosses a security boundary rather than staying inside a single trust context. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, i.e. every Chrome build prior to 155.0.8059.39, tracked upstream as Chromium issue 527023137 and in the EU as EUVD-2026-93797. No non-default configuration dependency is indicated - standard Chrome with Site Isolation enabled (the default) is the target.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Remote crafted-page delivery (AV:N/AC:L/PR:N) requires the victim to visit the page (UI:R); SiteIsolation bypass crosses the security boundary (S:C) enabling code execution with full CIA impact.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Incorrect Authorization in SiteIsolation in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome versions prior to 155.0.8059.39 contain a critical authorization flaw (CVE-2026-102322) that can allow an attacker to execute code on a user's workstation when they browse a malicious or compromised website. No public exploit identified at time of analysis, but the high severity and broad Chrome deployment mean a single successful attack could lead to data theft, lateral movement, or disruption. Security leadership should prioritize rapid patching because unpatched endpoints remain exposed to drive-by or social-engineering delivery.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
EUVD-2026-93797
GHSA-8pm8-72rp-hgvp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB