Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconCraft malicious Chrome Extension
-
DeliveryDistribute via Web Store or phishing
-
ExploitConvince user to install extension
-
InstallExtension executes in browser context
-
C2Bypass cross-origin access controls in Extensions subsystem
-
ExecuteRead data from cross-origin pages user visits
-
ImpactExfiltrate captured data to attacker
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 the target user to actively install a specifically crafted malicious Chrome Extension on an unpatched Chrome version prior to 151.0.7922.72 - the CVSS UI:R metric confirms that this user-driven installation step is mandatory and non-negotiable for exploitation. The extension must be crafted to abuse the specific cross-origin access control flaw; installing arbitrary extensions does not trigger the vulnerability. Exploitation is further constrained by: Chrome's extension installation permission dialogs which warn users about extension permissions, the Chrome Web Store's review process (circumventable via sideloading or compromised listings), and the scoped confidentiality-only impact (C:L, I:N, A:N) limiting damage to partial data exposure within the browser context. There is no drive-by, zero-click, or network-adjacent exploitation path - the social engineering prerequisite is the primary gating factor for real-world risk. |
| Impact | The CVSS 4.3 Medium score and vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N accurately capture the constrained nature of this vulnerability: while it is network-reachable and low-complexity, it requires active user interaction (UI:R) - specifically the installation of a malicious extension - and results in only limited confidentiality impact (C:L) with no integrity or availability exposure. EPSS of 0.13% at the 3rd percentile strongly aligns with the practical barrier posed by the social engineering prerequisite, indicating this is not being exploited in mass campaigns. The absence of a CISA KEV entry and lack of any public exploit code further support treating this as a routine patch cadence item rather than an emergency response priority. The 'Authentication Bypass' tag in the source intelligence appears inconsistent with the described cross-origin data leakage mechanism; this may reflect imprecise tagging rather than a distinct bypass capability, and no conflicting CVSS signals emerge from the vector itself. Overall, real-world risk is low for organizations with managed extension policies; consumer Chrome users relying on unreviewed extension installs face marginally higher exposure. |
| Exploit ScenarioDerived | An attacker publishes or distributes a crafted Chrome Extension - disguised as a productivity tool, ad blocker, or utility - and convinces a target user to install it via phishing, a deceptive Web Store listing, or direct sideloading. Once installed on an unpatched Chrome version, the extension exploits the improper access control flaw to silently read data from cross-origin pages the user subsequently visits, such as session identifiers or form content from authenticated web applications. No public proof-of-concept has been identified, but the low attack complexity (AC:L) in the CVSS vector suggests the exploit logic requires minimal technical sophistication once the extension installation hurdle is cleared. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
Cross-origin data leakage in Google Chrome's Extensions subsystem prior to version 151.0.7922.72 enables a crafted extension to bypass same-origin policy protections and read data from cross-origin browser contexts. Exploitation requires convincing a target user to install a malicious Chrome Extension, placing this firmly in the social-engineering-dependent threat category. No active exploitation is confirmed (not in CISA KEV), no public POC has been identified, and an EPSS of 0.13% at the 3rd percentile reflects minimal real-world exploitation probability at time of analysis.
RemediationAI
Update Google Chrome to version 151.0.7922.72 or later, the confirmed patched release per the Chrome Stable Channel Update advisory at http://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html. Chrome auto-updates by default; administrators can verify or force the update via chrome://settings/help or through enterprise management platforms (Google Admin Console, Microsoft Intune). As a compensating control before patching - or as a defense-in-depth measure - enterprise administrators should enforce an extension allowlist via Chrome's ExtensionInstallAllowlist and ExtensionInstallBlocklist Group Policy settings, permitting only vetted, approved extensions; this directly eliminates the social engineering vector this vulnerability requires. Additionally, disabling developer mode extensions (DeveloperToolsAvailability policy) prevents sideloading of unsigned extensions outside the Web Store review pipeline. Both controls carry the trade-off of reduced user flexibility but substantially reduce the attack surface for this and similar extension-based vulnerabilities.
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 extension platform implements the Chromium Extension API with cross-origin isolation controls intended to prevent extensions from accessing content across origins without explicit permission grants. CWE-284 (Improper Access Control) identifies the root cause as a failure in enforcing those access controls within the Extensions subsystem - a crafted extension can circumvent the same-origin policy boundary and read data from pages of differing origins that the user is visiting. The affected component spans all Chrome desktop releases below 151.0.7922.72, as reflected in CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering Windows, macOS, and Linux platforms. The Chromium issue tracker entry (https://issues.chromium.org/issues/513502990) is the upstream record of the flaw, reported by the Chrome security team.
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:L/I:N/A:N
Attacker delivers extension over network (AV:N), no special conditions needed (AC:L), no attacker credentials required (PR:N), user must install extension (UI:R), limited cross-origin data read with no write or availability impact (C:L/I:N/A:N).
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
Inappropriate implementation in Extensions in Google Chrome prior to 151.0.7922.72 allowed an attacker who convinced a user to install a malicious extension to leak cross-origin data via a crafted Chrome Extension. (Chromium security severity: Medium)
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 Multiple Security Flaws
View all 80Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-50730
GHSA-x4cw-wg5h-4qx6
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB