Description
Inappropriate implementation in FoldableAPIs in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Low)
Published: 2026-06-04
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The FoldableAPIs component of Google Chrome implements functionality that, before version 149.0.7827.53, contains an inappropriate construction that allows a remote attacker who has already compromised the renderer process to bypass site isolation. The flaw is a misuse of security controls that normally enforce process isolation for each site, corresponding to CWE‑1140—Incorrect Use of Security Features. While the Chromium team rates this issue as low severity, it still permits isolation break between sites, exposing data from other tabs or sites that share the same process space.

Affected Systems

Google Chrome browsers less than version 149.0.7827.53 are affected. This encompasses all desktop installations running those legacy builds.

Risk and Exploitability

Exploitation requires compromising the renderer process, typically through a malicious site that has already bypassed normal protection mechanisms. Once renderer control is achieved, the attacker can serve a crafted HTML page to the vulnerable component and force Chrome to treat remote content as part of the same site. Because the EPSS score is unavailable and the vulnerability is not listed in CISA KEV, the potential for widespread exploitation is currently low, though the impact on isolation between tabs remains significant. The low Chromium severity suggests that the overall risk to system integrity is modest but isolation boundaries can be broken.

Generated by OpenCVE AI on June 5, 2026 at 04:45 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to Chrome version 149.0.7827.53 or newer, as released by Google.
  • If an upgrade cannot be performed immediately, enable the "Site Per Process" flag in chrome://flags or launch Chrome with the "--site-per-process" command line option to enforce isolation for all sites.
  • Keep Chrome’s auto‑update enabled and monitor for future security releases.

Generated by OpenCVE AI on June 5, 2026 at 04:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 05 Jun 2026 05:00:00 +0000

Type Values Removed Values Added
Title FoldableAPIs Site Isolation Bypass in Chrome
Weaknesses CWE-1140

Thu, 04 Jun 2026 23:15:00 +0000

Type Values Removed Values Added
Description Inappropriate implementation in FoldableAPIs in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Low)
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Chrome

Published:

Updated: 2026-06-04T23:05:55.244Z

Reserved: 2026-06-04T17:10:58.607Z

Link: CVE-2026-11234

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-06-04T23:17:31.293

Modified: 2026-06-04T23:17:31.293

Link: CVE-2026-11234

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-06-05T04:45:32Z

Weaknesses