Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts CSP-bypassing HTML page
-
DeliveryDelivers link to victim via phishing or malicious ad
-
ExploitVictim clicks link in Chrome prior to 149.0.7827.53
-
ExecutionBlink fails to enforce site's CSP directives
-
PersistUnauthorized script or resource executes in page context
-
ImpactAttacker 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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 72Same weakness CWE-693 – Protection Mechanism Failure
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
EUVD-2026-34753
GHSA-hf37-2h38-4573
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB