Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSocial engineer victim via phishing or fake software offer
-
DeliveryConvince victim to install crafted Chrome extension
-
ExploitExtension loaded by Chrome prior to 152.0.7977.65
-
ExecutionIncorrect authorization check bypassed in Extensions subsystem
-
PersistSystem access restrictions circumvented
-
ImpactUnauthorized integrity-level action executed
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 | The target must be running Google Chrome prior to 152.0.7977.65 on a desktop platform. Mandatory user interaction (UI:R per CVSS) is the central limiting condition: the victim must be socially engineered into installing a crafted Chrome extension - no drive-by or passive exploitation path is indicated. No authentication or elevated privileges are required on the attacker's side (PR:N). No special server-side configuration or non-default Chrome deployment mode is required for the vulnerability to be present. Exploitation is limited to integrity impact only; confidentiality and availability are not compromised. Environments with enterprise extension install policies (allowlist enforcement) are not exploitable via this vector, as the crafted extension cannot be installed. |
| Impact | The CVSS base score of 4.3 (Medium) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N reflects a network-accessible flaw requiring no privileges but demanding mandatory user interaction (UI:R), which is the critical limiting factor. The attack chain depends entirely on social engineering to induce a user to install a malicious extension - this substantially reduces the likelihood of opportunistic or automated mass exploitation. Impact is bounded to integrity only (I:L), with no confidentiality or availability consequences confirmed. EPSS at 0.21% (11th percentile) is consistent with this profile and does not suggest active or widespread exploitation. The absence of a CISA KEV listing and no known POC further support treating this as a routine patch-cycle priority rather than an emergency response item. The social engineering prerequisite also means technical mitigations (enterprise extension policies) can meaningfully reduce exposure even before patching. |
| Exploit ScenarioDerived | An attacker hosts a website or phishing page that convinces a target running Chrome prior to 152.0.7977.65 to install a crafted Chrome extension - for example, by impersonating a legitimate productivity tool. Once installed, the malicious extension exploits the incorrect authorization logic in Chrome's Extensions subsystem to bypass system access restrictions it would normally be denied, achieving unauthorized integrity impact on the victim's system. No public exploit code has been identified at time of analysis, so exploitation currently requires a custom-crafted extension and social engineering capability. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 28, 2026
Incorrect authorization in Google Chrome's Extensions subsystem (versions prior to 152.0.7977.65) permits a remote attacker to bypass system access restrictions through a crafted Chrome extension delivered via social engineering. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N) confirms mandatory user interaction limits opportunistic exploitation, and impact is constrained to integrity with no confidentiality or availability consequence. No public exploit code or CISA KEV listing has been identified; EPSS at 0.21% (11th percentile) reflects low current exploitation probability consistent with the social-engineering dependency.
RemediationAI
Update Google Chrome to version 152.0.7977.65 or later using Chrome's built-in auto-update mechanism or by following the stable channel release guidance at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. As a compensating control before patching, enterprise administrators can restrict extension installation to an approved allowlist using Chrome enterprise policies (ExtensionInstallAllowlist and ExtensionInstallBlocklist via Group Policy or Google Admin); this prevents installation of untrusted crafted extensions and directly closes the social-engineering delivery vector, though it requires administrative overhead to maintain the allowlist. End-user awareness training against phishing and fake extension delivery is a secondary control with no technical trade-offs but variable effectiveness. No workaround fully substitutes 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
The vulnerability resides in Google Chrome's Extensions subsystem, rooted in CWE-863 (Incorrect Authorization) - a failure to verify that a requesting actor's permissions actually align with the resource or action being requested. Chrome's extension permission model is designed to gate what installed extensions can access or modify on the underlying system; this flaw allows a specially crafted extension to circumvent those gates. All Chrome desktop installations prior to 152.0.7977.65 are affected, as identified by CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*. The Chromium issue tracker entry (https://issues.chromium.org/issues/505951430) may contain additional internal technical detail not available in public advisories.
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
Social engineering delivery mandates UI:R; no privileges needed; integrity-only bypass with no confidentiality or availability impact confirmed in 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 Extensions in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to bypass system access restrictions 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.
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-65883
GHSA-f6v4-57jr-pm94
NVD
CVE.org
EPSS
Exploit-DB