CVE-2026-8568
Google Chrome AI Insufficient Policy Enforcement Remote Code Execution
Description
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)
INFO
Published Date :
May 14, 2026, 8:17 p.m.
Last Modified :
May 19, 2026, 3:18 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | LOW | 134c704f-9b21-4f2e-91b3-4a467353bcc0 |
Solution
- Update Google Chrome to the latest version.
- Ensure AI policies are strictly enforced.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-8568.
| URL | Resource |
|---|---|
| https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html | Vendor Advisory |
| https://issues.chromium.org/issues/488728570 | Permissions Required |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-8568 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-8568
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-8568 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-8568 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
May. 19, 2026
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* versions up to (excluding) 148.0.7778.168 Added Reference Type Chrome: https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html Types: Vendor Advisory Added Reference Type Chrome: https://issues.chromium.org/issues/488728570 Types: Permissions Required -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
May. 15, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N Added CWE CWE-693 -
New CVE Received by [email protected]
May. 14, 2026
Action Type Old Value New Value Added Description 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) Added Reference https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html Added Reference https://issues.chromium.org/issues/488728570