VulnerabilityPublished 4 Jun 2026

CVE-2026-11234: Google Chrome · Insufficient Policy Enforcement

Affects Google ChromeSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 149.0.7827.53 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 149.0.7827.53

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Chrome and google/chrome to 149.0.7827.53.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=149.0.7827.53 <149.0.7827.53	Fixed in 149.0.7827.53
Googlegoogle/chrome`pkg:deb/google/chrome`Other threats	Affected <149.0.7827.53	Fixed in 149.0.7827.53

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The provided vendor advisory link should be monitored for updates on fixes or mitigations.

Description

CVE-2026-11234 is a vulnerability in Google Chrome's FoldableAPIs prior to version 149.0.7827.53. It allows a remote attacker who has compromised the renderer process to bypass site isolation by using a crafted HTML page. The vulnerability has a medium severity rating with a CVSS score of 4.3. No known exploits are reported in the wild. The vendor advisory does not explicitly confirm a patch or remediation status.

Impact

The vulnerability allows bypassing site isolation, potentially exposing data across site boundaries if the renderer process is compromised. The impact is limited to confidentiality with no reported effects on integrity or availability. There are no known exploits in the wild, indicating limited or no active exploitation at this time.

Summary

This vulnerability involves insufficient policy enforcement in the FoldableAPIs component of Google Chrome before version 149.0.7827.53. An attacker with control over the renderer process can bypass site isolation protections through a crafted HTML page. Site isolation is a security feature designed to separate different websites into different processes to prevent data leaks. The issue is classified under CWE-693 (Protection Mechanism Failure). The CVSS 3.1 vector indicates the attack requires no privileges and user interaction but can be executed remotely with low complexity, impacting confidentiality with no impact on integrity or availability.

CWE-693Protection Mechanism Failure (opens in a new tab)
Pillar weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Cross Site Tracing (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Encryption Brute Forcing (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jun 2026, 10:46 UTC

WeaknessesCWE-693

Technical details

References

Community reviews

Related threats