Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts malicious HTML page
-
DeliveryVictim lured via phishing or malvertising
-
ExploitVictim navigates to page in unpatched Chrome
-
ExecutionFileSystem authorization check bypassed
-
ImpactUnauthorized write to restricted filesystem scope
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 victim must be running Google Chrome prior to version 152.0.7977.65 on a desktop platform. The sole prerequisite for exploitation is that the victim navigates to an attacker-controlled HTML page - this is the user interaction (CVSS UI:R) that limits opportunistic exploitation. No special Chrome configuration, non-default settings, or authenticated session is required on the attacker side (PR:N, AC:L). The primary limiting factor is the social-engineering dependency: the attacker must convince the user to visit the crafted page. Impact is bounded to integrity (I:L) - unauthorized filesystem writes within the scope of the bypass - with no confidentiality exposure or service disruption. |
| Impact | The CVSS 3.1 base score of 4.3 (Medium) is internally consistent: network-delivered (AV:N), low complexity (AC:L), no attacker privileges required (PR:N), but user interaction required (UI:R), with limited integrity impact only (I:L) and no scope change. The UI:R requirement is the primary risk-dampening factor - opportunistic mass exploitation is constrained because the victim must visit a crafted page. EPSS at 0.27% (19th percentile) corroborates low current exploitation interest. Absence from CISA KEV and no referenced POC further reduce urgency. Despite Chrome's ubiquitous deployment footprint, the combination of medium CVSS, low EPSS, user-interaction dependency, and integrity-only impact makes this a routine patch-cycle priority rather than an emergency response item. No conflicting signals were identified in the available intelligence. |
| Exploit ScenarioDerived | An attacker registers a domain and hosts a crafted HTML page that triggers Chrome's FileSystem authorization flaw when rendered by the browser. The attacker delivers the link via phishing email or malicious advertisement, and once the victim navigates to the page, the authorization bypass executes without further interaction, allowing the page to perform unauthorized filesystem writes beyond its sandboxed origin. No public proof-of-concept code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 28, 2026
Chrome's FileSystem API implementation prior to version 152.0.7977.65 contains incorrect authorization logic (CWE-863) that permits a remote attacker to bypass system access restrictions by directing a user to a crafted HTML page via social engineering. The bypass produces a limited integrity impact - unauthorized write or access to filesystem-restricted resources - with no confidentiality or availability consequence per the CVSS vector (I:L, C:N, A:N). No public exploit code exists and the vulnerability is absent from CISA KEV; EPSS of 0.27% (19th percentile) reflects low near-term exploitation probability.
RemediationAI
Update Google Chrome to version 152.0.7977.65 or later, as documented in the vendor's stable channel release at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Chrome's auto-update mechanism handles this for most consumer deployments, but enterprise administrators should verify rollout via Google Admin Console, Chrome Browser Cloud Management, or endpoint management tooling. As a compensating control before patching, restricting outbound browsing to known-trusted domains via a web proxy or browser enterprise policy (URLBlocklist) reduces exposure to attacker-controlled pages; the trade-off is operational friction for users accessing external web content. Disabling the FileSystem API via Chrome enterprise policy (if supported in the deployed version) would eliminate the attack surface but may break progressive web applications that depend on it.
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 Chrome's FileSystem API, which governs sandboxed web-origin access to local filesystem storage. CWE-863 (Incorrect Authorization) indicates the authorization check that enforces origin or scope boundaries on filesystem operations can be bypassed via a specially crafted HTML page - the page likely exploits a logic error in how the FileSystem subsystem validates permissions before granting access. The affected CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covers all Chrome desktop builds prior to 152.0.7977.65 on Windows, macOS, and Linux. The Chromium issue tracker reference (issues.chromium.org/issues/514454739) points to an internal security bug report consistent with a Chromium-team-reported finding.
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 passive user navigation; no attacker privileges needed; impact is integrity-only filesystem write bypass with no data disclosure or availability loss.
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 FileSystem in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to bypass system access restrictions via a crafted HTML page. (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-65922
GHSA-m39q-r48h-w52v
NVD
CVE.org
EPSS
Exploit-DB