VulnerabilityPublished 8 Jun 2026

CVE-2026-11653: Google Chrome · Insufficient Validation of Untrusted Input

Affects Google ChromeSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 149.0.7827.103 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.5Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: High
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 8 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 Google Chrome to 149.0.7827.103.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=149.0.7827.103 <149.0.7827.103	Fixed in 149.0.7827.103

AI-suggested

Google has released Chrome version 149.0.7827.103 which addresses this vulnerability. Users and administrators should update to this version or later to remediate the issue. Since this is a client-side vulnerability in a desktop browser, patching the affected software is the primary mitigation. No additional vendor advisories indicate alternative mitigations or that the issue is already mitigated without patching.

Description

CVE-2026-11653 is a vulnerability in Google Chrome prior to version 149.0.7827.103 where improper validation of untrusted input in Extensions allowed a remote attacker with control over the renderer process to bypass site isolation using a crafted HTML page. The issue is rated with a medium severity and has a CVSS score of 6.5. No known exploits in the wild have been reported. The vulnerability affects Chrome versions before 149.0.7827.103.

Impact

The vulnerability allows an attacker who has compromised the renderer process to bypass site isolation, potentially enabling unauthorized interactions or manipulations across site boundaries within the browser. This could undermine the security guarantees provided by site isolation, increasing the risk of cross-site attacks or data integrity violations. However, the vulnerability does not impact confidentiality or availability directly. No known exploits have been reported in the wild at this time.

Summary

This vulnerability involves insufficient validation of untrusted input in the Extensions component of Google Chrome before version 149.0.7827.103. An attacker who has already compromised the renderer process could exploit this flaw by crafting a malicious HTML page to bypass Chrome's site isolation security feature. Site isolation is a critical defense mechanism designed to separate different websites into different processes to prevent data leaks and cross-site attacks. The CVSS 3.1 vector indicates the attack requires network access, low attack complexity, no privileges, and user interaction, resulting in a high impact on integrity but no impact on confidentiality or availability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Jun 2026, 08:40 UTC

Technical details

References

Community reviews

Related threats