Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Lifecycle Timeline
3DescriptionCVE.org
Insufficient policy enforcement in AI in Google Chrome prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to bypass Site Isolation via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Site Isolation bypass in Google Chrome prior to 148.0.7778.168 allows remote attackers who have already compromised the renderer process to access cross-site data via crafted HTML pages. The vulnerability affects Chrome's AI policy enforcement, enabling a second-stage attack after initial renderer compromise. Attack complexity is high, requiring both initial renderer compromise and user interaction. EPSS score of 0.02% indicates very low exploitation probability, and no active exploitation or public POC has been identified. Vendor patch is available in Chrome 148.0.7778.168.
Technical ContextAI
This vulnerability exploits insufficient policy enforcement in Google Chrome's AI features, classified under CWE-693 (Protection Mechanism Failure). Site Isolation is Chrome's fundamental security architecture that segregates content from different origins into separate renderer processes to prevent cross-site data leakage. The AI policy layer appears to have enforcement gaps that allow a compromised renderer to escape its sandboxed origin context. The attack requires initial renderer compromise as a prerequisite, making this a post-exploitation technique rather than an initial access vector. The CVSS vector shows network-based attack (AV:N) but high complexity (AC:H) and required user interaction (UI:R), with impact limited to low confidentiality breach (C:L) and no scope change (S:U), indicating the attacker remains constrained to the Chrome security boundary despite bypassing Site Isolation internally.
RemediationAI
Upgrade to Google Chrome version 148.0.7778.168 or later, which contains the patch for this vulnerability as confirmed in the May 2026 Stable Channel Update at chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html. Chrome's automatic update mechanism will deploy this fix to most installations within 48-72 hours of release. Enterprise administrators using managed Chrome deployments should verify update policies allow timely patching or manually push version 148.0.7778.168 via management consoles. For environments where immediate patching is not feasible, implement defense-in-depth controls: disable Chrome AI features if enterprise policy allows (reduces attack surface but may impact user functionality requiring AI capabilities), enforce strict Content Security Policy headers on web applications to limit renderer compromise vectors, and monitor for signs of renderer exploitation through endpoint detection tools. Note that no workaround fully mitigates the Site Isolation bypass once renderer compromise occurs - patching remains the only complete remediation. Technical details at Chromium bug tracker issues/488728570 may inform additional hardening measures.
Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
Same weakness CWE-693 – Protection Mechanism Failure
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-30388
GHSA-3j3h-g4g8-qvq9