VulnerabilityPublished 4 Jun 2026

CVE-2026-11267: 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, 20:25 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 3% 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:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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

Until confirmation of a fix, users should avoid installing untrusted extensions and apply updates promptly once available.

Description

CVE-2026-11267 is a vulnerability in Google Chrome prior to version 149.0.7827.53 involving insufficient policy enforcement in browser extensions. This flaw allows an attacker who convinces a user to install a malicious extension to bypass the content security policy. The vulnerability has a medium severity rating with a CVSS score of 4.3. No known exploits are reported in the wild. A vendor advisory link is provided but does not explicitly confirm patch availability or remediation status.

Impact

An attacker who successfully convinces a user to install a crafted malicious Chrome extension can bypass the content security policy, potentially leading to integrity impacts within the browser environment. There is no impact on confidentiality or availability. The vulnerability requires user interaction and has low attack complexity.

Summary

This vulnerability (CVE-2026-11267) affects Google Chrome versions before 149.0.7827.53. It arises from insufficient enforcement of policies in Chrome extensions, enabling a malicious extension to bypass the content security policy. The issue requires user interaction, specifically convincing the user to install the malicious extension. The CVSS vector indicates network attack vector, low attack complexity, no privileges required, user interaction required, unchanged scope, no confidentiality impact, low integrity impact, and no availability impact. The vendor advisory link is available but does not explicitly state if the issue is fixed in version 149.0.7827.53 or later.

CWE-602Client-Side Enforcement of Server-Side Security (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product includes a server that relies on the client to implement a protection mechanism that is intended to protect the server.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely.
Architecture and Design
If some degree of trust is required between the two entities, then use integrity checking and strong authentication to ensure that the inputs are coming from a trusted source.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.1 (opens in a new tab)
V1.5.3 (opens in a new tab)
V4.1.1 (opens in a new tab)
Attack patterns
Manipulating Hidden Fields (opens in a new tab)
Create Malicious Client (opens in a new tab)
Removing Important Client Functionality (opens in a new tab)
Removing/short-circuiting 'Purse' logic: removing/mutating 'cash' decrements (opens in a new tab)
Accessing/Intercepting/Modifying HTTP Cookies (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:22 UTC

WeaknessesCWE-602

Technical details

References

Community reviews

Related threats