Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost crafted HTML page on attacker-controlled server
-
DeliveryDeliver page URL to victim via phishing or malicious ad
-
ExploitVictim visits page in Chrome < 149.0.7827.53
-
ExecutionCrafted page triggers Content Settings enforcement flaw
-
PersistBypass discretionary access control policy
-
ImpactAchieve limited integrity modification of browser permission state
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target is running Google Chrome prior to version 149.0.7827.53 and visits a crafted HTML page controlled by the attacker (UI:R per CVSS vector). The CVSS vector confirms the attacker requires no authentication (PR:N) and no special server configuration - any web server hosting the malicious page suffices. Exploitation is concretely limited by the mandatory user interaction requirement: the victim must navigate to or be redirected to the attacker-controlled page, introducing a social engineering dependency. The vulnerability affects Chrome's Content Settings enforcement layer specifically; the impact is bounded to a limited integrity bypass (I:L) with no confidentiality or availability consequence, meaning an attacker cannot read data or crash the browser through this flaw alone. Environments where Chrome Content Settings are not relied upon as a meaningful security boundary face reduced practical risk. |
| Impact | The CVSS 4.3 base score reflects a narrow, integrity-only impact (I:L) with no confidentiality or availability consequences, meaningfully limiting the damage potential. The network attack vector (AV:N) and low complexity (AC:L) lower the bar for exploitation, but the mandatory user interaction (UI:R) introduces a social engineering dependency - a victim must be directed to a crafted page. No EPSS data was supplied in the intelligence sources, so probabilistic exploitation likelihood cannot be quantified from this dataset. The vulnerability is not listed in CISA KEV, no POC has been identified, and Google's internal severity rating is Low - all signals converge on low real-world priority. For enterprises using Chrome's Content Settings policies as an enforced security boundary (e.g., managed browser fleets with policy-mandated permission restrictions), risk is slightly elevated; for standard consumer deployments, this is a routine patch-cycle item. No conflicting signals were identified in the available data. |
| Exploit ScenarioDerived | An attacker crafts a malicious HTML page that triggers Chrome's Content Settings policy enforcement flaw and distributes the URL via phishing email or malicious advertisement targeting users running Chrome prior to 149.0.7827.53. When a victim navigates to the page, Chrome's insufficient policy enforcement allows the page to bypass intended Content Settings access controls, potentially overriding site permission restrictions that a managed or security-conscious user would expect to be enforced. No public exploit or POC has been identified at time of analysis, meaning realistic exploitation currently requires independent capability to discover and implement the bypass technique. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 05, 2026
Content Settings policy enforcement bypass in Google Chrome prior to 149.0.7827.53 enables remote attackers to circumvent discretionary access control by delivering a crafted HTML page to a victim who must interact with it. Rooted in CWE-284 (Improper Access Control), the flaw affects Chrome's Content Settings subsystem - which governs site-level permissions such as cookies, notifications, and script access - yielding a limited integrity impact with no confidentiality or availability consequences. No public exploit has been identified and the vulnerability is absent from CISA KEV; the vendor itself rates this as Low severity, consistent with the CVSS 4.3 base score.
RemediationAI
The primary remediation is to upgrade Google Chrome to version 149.0.7827.53 or later, which is confirmed available per the vendor's stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Enterprise environments managing Chrome via group policy or device management platforms (Google Admin Console, Intune) should deploy this update through their standard software distribution pipeline. As a temporary compensating control for environments unable to patch immediately, administrators can enforce maximally restrictive Content Settings via Chrome enterprise policy templates to reduce the permission surface exploitable through this flaw; note this may disrupt legitimate site functionality relying on browser-managed permissions. No additional vendor-documented workarounds are available beyond applying the update.
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
Google Chrome's Content Settings subsystem enforces per-origin access control policies governing browser-level permissions including JavaScript execution, cookies, camera, microphone, and notifications. CWE-284 (Improper Access Control) identifies the root cause as a failure to correctly enforce these policies at the content-settings layer when parsing or rendering a specially constructed HTML document. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) confirms this is network-reachable with low attack complexity and no required privileges, but requires user interaction - indicating the exploit payload is delivered via a web page the victim must visit. Scope:Unchanged means the flaw does not escape Chrome's process boundary into the underlying OS or other applications. The Chromium issue tracker entry (issues.chromium.org/issues/498373018) is the upstream technical reference for the fix.
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 Content Settings in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass discretionary access control 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-284 – Improper Access Control
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
EUVD-2026-34713
GHSA-5mqf-cxmj-6pgf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB