Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify and profile target Chrome user
-
DeliveryDeliver renderer-level exploit via malicious web content
-
ExploitCompromise renderer process
-
ExecutionServe crafted HTML page triggering Extensions authorization flaw
-
PersistBypass web origin policy
-
ImpactAccess privileged browser-internal or extension page content
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 two sequential preconditions: first, the attacker must have already compromised the Chrome renderer process via a separate, independent vulnerability - this is not a standalone exploit path; second, the target user must render or visit a crafted HTML page (user interaction required, UI:R). The flaw is in the Extensions subsystem and is present regardless of which browser extensions are installed. Key limiting factors: renderer compromise is a high technical bar that restricts realistic exploitation to sophisticated threat actors capable of chaining multiple browser bugs; and user interaction is required, ruling out fully automated or passive exploitation. Authentication is not a constraint per the PR:N CVSS metric, but the renderer compromise prerequisite effectively functions as an implicit access requirement not captured in the base score. |
| Impact | The vendor-assigned CVSS 4.3 score (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) encodes a medium-severity network-reachable flaw requiring user interaction, with limited confidentiality impact and no integrity or availability impact. However, the CVSS AC:L rating is likely underestimated: the CVE description explicitly requires a pre-existing renderer compromise as a prerequisite, which is a substantial technical bar absent from the CVSS encoding and which would warrant AC:H in an independent assessment. EPSS at 0.24% (15th percentile) corroborates low observed exploitation probability in the wild. The CVE is not in CISA KEV, and no public exploit code has been identified. The realistic threat model is a sophisticated browser exploit chain - an attacker exploits one renderer-level bug first, then pivots using this flaw - placing successful exploitation firmly in the domain of advanced threat actors rather than opportunistic or automated attacks. |
| Exploit ScenarioDerived | An attacker targeting a specific user first exploits a separate renderer-level vulnerability - such as a V8 JavaScript engine bug - to compromise the Chrome renderer process, then serves a crafted HTML page that exercises the Extensions subsystem authorization flaw to break web origin isolation and read content from a privileged browser-internal page. No public exploit code for CVE-2026-79174 has been identified; successful exploitation requires chaining at least two distinct Chrome vulnerabilities. |
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 (all versions before 152.0.7977.65) allows an attacker who has already compromised the renderer process to bypass the web origin policy and reach privileged browser pages via a crafted HTML page. This is a chained, second-stage vulnerability - a prior renderer compromise is required - substantially narrowing the realistic attacker pool despite the network-accessible vector. No active exploitation is confirmed (not listed in CISA KEV), and the EPSS probability of 0.24% at the 15th percentile is consistent with this chained attack profile.
RemediationAI
Update Google Chrome to version 152.0.7977.65 or later; this is the vendor-confirmed fixed release per the Chrome stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Chrome updates automatically for consumer installations; enterprise administrators should verify deployment via Google Update, Intune, or their endpoint management platform and confirm the installed version reaches 152.0.7977.65. As a compensating control where immediate patching is infeasible, restricting which extensions are permitted via Chrome enterprise policy (ExtensionInstallBlocklist, ExtensionAllowedTypes) reduces the privileged surface exposed through the Extensions subsystem, though this does not eliminate the underlying authorization flaw. Since exploitation requires a renderer compromise as a precondition, maintaining patch currency for all Chrome renderer-level vulnerabilities is the most effective systemic defense.
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 affected component is Chrome's Extensions subsystem, which enforces the authorization boundary between web-rendered content (running in the sandboxed renderer process) and privileged browser contexts such as extension background pages and chrome:// internal pages. CWE-863 (Incorrect Authorization) identifies the root cause: the subsystem fails to correctly reject requests originating from a compromised renderer process, allowing that process to bypass the web origin policy - Chrome's core isolation mechanism - and access privileged page contexts it should not reach. The affected product is identified by CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Google Chrome desktop releases prior to 152.0.7977.65 across all supported platforms.
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
AC:H reflects the mandatory renderer compromise precondition absent from the vendor vector; all other metrics align with the description and vendor scoring.
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 who had compromised the renderer process to bypass web origin policy into a privileged page via a crafted HTML page. (Chromium security severity: High)
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-65801
GHSA-pmxj-692w-95v8
NVD
CVE.org
EPSS
Exploit-DB