Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker hosts crafted HTML page
-
DeliveryUser clicks link or is redirected to page
-
ExploitChrome's Select component performs incorrect origin authorization check
-
ExecutionSame-origin policy boundary bypassed
-
ImpactAttacker script executes limited cross-origin integrity action
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a user to actively navigate to an attacker-controlled HTML page using a vulnerable Chrome version (below 152.0.7977.65) - the CVSS UI:R metric confirms passive drive-by exploitation without user navigation is not applicable. No authentication is required from the attacker's perspective (PR:N), and no special server-side configuration is needed; the attack is delivered entirely via a crafted HTML page. Impact is constrained to integrity only (I:L) with no confidentiality or availability effect, and scope is contained to the vulnerable Chrome instance (S:U), meaning the attacker cannot pivot to other system components. The primary limiting factors are the mandatory user interaction and the narrow, integrity-only impact ceiling. |
| Impact | The CVSS 4.3 score reflects a network-reachable, low-complexity attack requiring no privileges but mandatory user interaction (UI:R), scoped to the vulnerable system with integrity-only impact (I:L, C:N, A:N). These signals collectively indicate a real but bounded risk: the attacker cannot passively exploit; a user must navigate to the crafted page. EPSS at 0.26% (18th percentile) is notably low and aligns with Chromium's own Low severity designation, suggesting the vulnerability class is not attractive to automated exploitation pipelines. There is no CISA KEV listing and no known public exploit, further reducing urgency. The integrity-only, non-scoped impact means even a successful exploit does not expose credentials or crash the browser - it produces limited unauthorized cross-origin actions. While the ubiquitous deployment of Chrome means the total exposed population is enormous in absolute terms, the combination of required user interaction, low EPSS, no KEV, and minimal impact ceiling keeps this firmly in the patch-on-cycle rather than emergency-response tier. |
| Exploit ScenarioDerived | An attacker hosts a crafted HTML page that exploits the incorrect authorization in Chrome's Select component to bypass same-origin policy restrictions. When a victim using a vulnerable Chrome version navigates to the page - via a phishing link, malvertising redirect, or compromised site - the attacker's script performs limited unauthorized cross-origin integrity actions within the user's browsing session. No public exploit code has been identified at time of analysis, making opportunistic mass exploitation unlikely in the near term. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 26, 2026
Web origin policy bypass in Google Chrome prior to 152.0.7977.65 allows a remote attacker to circumvent same-origin restrictions via a crafted HTML page, achieving limited integrity impact in the user's browsing context. The flaw is rooted in incorrect authorization logic (CWE-863) within Chrome's Select component, as confirmed by the vendor's stable channel advisory. No public exploit has been identified at time of analysis, and EPSS signals very low exploitation probability at 0.26% (18th percentile), consistent with Chromium's own Low severity rating.
RemediationAI
Update Google Chrome to version 152.0.7977.65 or later, which contains the vendor-released patch as documented in the stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Enterprise environments should push the update via Google Admin Console managed browser policies or equivalent MDM tooling to ensure fleet-wide coverage. Prior to patching, compensating controls with limited effectiveness include restricting end-user browsing to known-trusted domains via enterprise URL filtering (trade-off: operational disruption) or enabling Chrome's Enhanced Safe Browsing mode to reduce exposure to attacker-hosted pages. Given the low EPSS and absence of active exploitation, standard patch cadence is appropriate rather than emergency deployment.
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
The vulnerability exists in the Select component of the Chromium rendering engine, the open-source core shared by Google Chrome and derivative browsers. CWE-863 (Incorrect Authorization) indicates the engine fails to correctly evaluate authorization decisions when handling Select interactions, allowing attacker-controlled page content to bypass web origin policy - the browser's foundational same-origin enforcement mechanism. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Chrome versions across platforms prior to 152.0.7977.65. Web origin policy governs cross-origin data access and action boundaries; a bypass in this layer can enable attacker script to interact with resources belonging to a different origin than the one that loaded it.
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
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Network-delivered via crafted page requiring active user navigation (UI:R); no privileges needed; integrity-only low impact with no confidentiality or availability effect confirmed by description.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
Lifecycle Timeline
3DescriptionCVE.org
Incorrect authorization in Select in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to bypass web origin 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.
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-66048
GHSA-7xq6-r3gc-f88g
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB