Skip to main content

Google Chrome CVE-2026-11292

| EUVDEUVD-2026-34753 MEDIUM
Protection Mechanism Failure (CWE-693)
2026-06-05 chrome-cve-admin@google.com GHSA-hf37-2h38-4573
4.3
CVSS 3.1 · Vendor: google
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker crafts CSP-bypassing HTML page
  2. Delivery
    Delivers link to victim via phishing or malicious ad
  3. Exploit
    Victim clicks link in Chrome prior to 149.0.7827.53
  4. Execution
    Blink fails to enforce site's CSP directives
  5. Persist
    Unauthorized script or resource executes in page context
  6. Impact
    Attacker achieves low-impact integrity violation

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
Exploitation Conditions

Exploitation requires that the victim is running Google Chrome prior to version 149.0.7827.53 and interacts with (visits) an attacker-controlled or attacker-influenced HTML page - user interaction (UI:R) is a confirmed hard prerequisite per the CVSS vector, meaning drive-by exploitation without any user action is not possible. No attacker privileges or authentication are required (PR:N per CVSS). For the bypass to produce meaningful impact, the targeted web application must have a Content Security Policy in place; sites not deploying CSP are unaffected by this specific vulnerability. Attack complexity is Low (AC:L), requiring no special timing, race condition, or privileged network position beyond delivering the crafted page. Exploitation is strictly bounded to low integrity impact (I:L) - this vulnerability cannot independently achieve code execution, credential theft, or denial of service.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) scores this at 4.3 Medium, reflecting a network-reachable, low-complexity attack requiring no attacker privileges but mandating user interaction - the victim must navigate to a crafted page. The Unchanged scope and absence of confidentiality or availability impact further constrain the worst-case outcome to minor integrity violations. EPSS at 0.02% (4th percentile) is extremely low, indicating the security community has assessed near-negligible near-term exploitation likelihood. This vulnerability is not listed in CISA KEV, no public exploit code has been identified, and Chromium's own severity assessment is Low. The tag 'Authentication Bypass' in source data is potentially misleading - this is more precisely a client-side policy enforcement bypass, not a server-side authentication bypass. Real-world priority is low for most organizations; however, enterprises that rely heavily on CSP as a defense-in-depth layer against XSS in sensitive web applications should treat patching as a routine but prompt update cycle task.

Exploit ScenarioDerived

An attacker registers or compromises a website and serves a crafted HTML page engineered to exploit the Blink CSP enforcement gap. A user running Chrome prior to 149.0.7827.53 is directed to this page - via phishing email, malicious advertisement, or a compromised legitimate site - and upon loading, the page bypasses CSP restrictions to load or execute unauthorized content within the browser context. No public exploit code has been identified at time of analysis, and the 0.02% EPSS score indicates this scenario has not materialized in observed threat activity.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 05, 2026

Content Security Policy bypass in Google Chrome's Blink rendering engine (versions prior to 149.0.7827.53) enables unauthenticated remote attackers to circumvent CSP directives by delivering a crafted HTML page that requires only a user visit to trigger. The impact is confined to low-severity integrity violations (CVSS I:L) with no confidentiality or availability consequences, consistent with Chromium's own Low severity rating. No public exploit has been identified at time of analysis, and an EPSS score of 0.02% (4th percentile) reflects negligible near-term exploitation probability.

RemediationAI

Upgrade Google Chrome to version 149.0.7827.53 or later, as confirmed by the vendor's stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's automatic update mechanism will deliver this version to most end-user installations without manual intervention; enterprise administrators managing browser deployment via policy (e.g., Google Admin Console or ADMX templates) should verify update propagation and confirm version compliance. As a compensating control before patching can be verified across a managed fleet, organizations relying on CSP for high-assurance protections against XSS in critical internal web applications should consider temporarily enforcing web proxy allowlisting to restrict navigation to untrusted external origins. Note that network-layer controls do not address the Blink enforcement flaw itself and carry the trade-off of reduced user browsing capability; they are not a substitute for the vendor patch.

Affected VersionsENISA

Chrome 149.0.7827.53 <149.0.7827.53

Affected Packages

euvd chrome fix: 149.0.7827.53

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Blink is the HTML rendering engine embedded in all Chromium-based browsers, responsible for parsing web content and enforcing browser security primitives including Content Security Policy. CSP is a declarative security mechanism that instructs the browser to restrict which resources (scripts, styles, frames, etc.) a page may load or execute, serving as a key mitigation against cross-site scripting and data injection. CWE-693 (Protection Mechanism Failure) identifies the root cause as a failure to correctly enforce an existing security control rather than an absence of one - the CSP logic is present in Blink but can be bypassed through insufficient enforcement in a specific code path. The affected component is the Blink engine within Google Chrome versions prior to 149.0.7827.53, as confirmed by EUVD affected version data. The Chromium issue tracker entry at https://issues.chromium.org/issues/502358901 is the upstream tracking reference, though the technical specifics of the enforcement gap are not detailed in available public data.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (google) PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
SUSE MEDIUM
Red Hat 5.4 LOW

Primary rating from Vendor (google).

CVSS VectorVendor: google

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

Lifecycle Timeline

3
CVSS changed
Jun 05, 2026 - 20:22 NVD
4.3 (MEDIUM)
CVE Published
Jun 05, 2026 - 00:17 nvd
UNKNOWN (no severity yet)
CVE Published
Jun 05, 2026 - 00:17 nvd
MEDIUM 4.3

DescriptionCVE.org

Insufficient policy enforcement in Blink in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass content security policy via a crafted HTML page. (Chromium security severity: Low)

Threat Intelligence Overview

EPSS Score
0.0%
Top 96% exploitable
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

Related Vulnerabilities in Google Chrome Security Fixes (149.0.7827.53)

View all 72
CVE-2026-11307 HIGH
8.8
CVE-2026-11238 MEDIUM
5.9
CVE-2026-11239 HIGH
7.5
CVE-2026-11240 LOW
3.1
CVE-2026-11241 HIGH
8.0
CVE-2026-11242 HIGH
7.5
CVE-2026-11243 MEDIUM
5.4
CVE-2026-11244 LOW
3.1
CVE-2026-11245 MEDIUM
4.3
CVE-2026-11246 MEDIUM
5.3
CVE-2026-11247 LOW
3.1
CVE-2026-11248 HIGH
8.8
CVE-2026-11249 MEDIUM
4.7
CVE-2026-11250 CRITICAL
9.6
CVE-2026-11251 LOW
3.1
CVE-2026-11252 MEDIUM
4.3
CVE-2026-11253 MEDIUM
4.3
CVE-2026-11254 MEDIUM
4.3
CVE-2026-11255 HIGH
7.5
CVE-2026-11256 HIGH
8.3
CVE-2026-11257 MEDIUM
4.3
CVE-2026-11258 MEDIUM
6.5
CVE-2026-11259 MEDIUM
4.3
CVE-2026-11260 MEDIUM
4.3
CVE-2026-11261 MEDIUM
4.3
CVE-2026-11262 HIGH
8.8
CVE-2026-11263 MEDIUM
6.5
CVE-2026-11264 MEDIUM
4.3
CVE-2026-11265 HIGH
7.5
CVE-2026-11266 MEDIUM
4.3
CVE-2026-11267 MEDIUM
4.3
CVE-2026-11268 MEDIUM
6.5
CVE-2026-11269 HIGH
7.1
CVE-2026-11270 MEDIUM
6.5
CVE-2026-11271 MEDIUM
6.5
CVE-2026-11272 HIGH
8.8
CVE-2026-11273 MEDIUM
6.1
CVE-2026-11275 MEDIUM
6.5
CVE-2026-11276 MEDIUM
5.1
CVE-2026-11277 MEDIUM
4.3
CVE-2026-11278 MEDIUM
6.5
CVE-2026-11280 MEDIUM
4.3
CVE-2026-11281 MEDIUM
5.0
CVE-2026-11282 CRITICAL
9.6
CVE-2026-11283 MEDIUM
6.5
CVE-2026-11284 MEDIUM
6.5
CVE-2026-11285 MEDIUM
4.3
CVE-2026-11286 MEDIUM
4.3
CVE-2026-11287 MEDIUM
6.5
CVE-2026-11288 MEDIUM
6.5
CVE-2026-11289 MEDIUM
6.5
CVE-2026-11290 MEDIUM
5.0
CVE-2026-11291 MEDIUM
4.3
CVE-2026-11293 CRITICAL
9.6
CVE-2026-11294 MEDIUM
4.3
CVE-2026-11295 HIGH
8.8
CVE-2026-11298 MEDIUM
4.3
CVE-2026-11299 MEDIUM
6.5
CVE-2026-11300 MEDIUM
4.3
CVE-2026-11301 HIGH
8.8
CVE-2026-11302 MEDIUM
4.3
CVE-2026-11308 MEDIUM
6.3
CVE-2026-11309 MEDIUM
4.3
CVE-2026-11274 MEDIUM
4.3
CVE-2026-11279 HIGH
8.8
CVE-2026-11296 HIGH
7.5
CVE-2026-11297 HIGH
7.7
CVE-2026-11303 HIGH
8.8
CVE-2026-11304 HIGH
8.8
CVE-2026-11305 HIGH
8.8
CVE-2026-11306 HIGH
8.8

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
openSUSE Tumbleweed Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy