EUVD-2026-40739
GHSA-qfv7-g547-v6hg
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Attacker serves a crafted HTML page (AV:N, PR:N), victim must navigate to it (UI:R), impact is limited integrity bypass within the browser sandbox (I:L, C:N, A:N, S:U).
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Insufficient policy enforcement in FileSystem in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to bypass discretionary access control via a crafted HTML page. (Chromium security severity: Low)
AnalysisAI
FileSystem policy enforcement bypass in Google Chrome prior to version 150.0.7871.47 allows a remote attacker to circumvent discretionary access control via a crafted HTML page, resulting in limited unauthorized write operations within the browser's sandboxed filesystem scope. The vulnerability requires user interaction - the victim must navigate to a malicious page - and produces only an integrity impact (I:L) with no confidentiality or availability consequence. With an EPSS of 0.18% (8th percentile) and no CISA KEV listing, real-world exploitation probability is very low; no public exploit has been identified at time of analysis.
Technical ContextAI
The flaw resides in Chrome's implementation of the FileSystem API, a browser capability that grants web applications controlled read/write access to a sandboxed local filesystem partition. CWE-284 (Improper Access Control) identifies the root cause: Chrome's internal security policies governing what filesystem operations a web origin is permitted to perform are insufficiently enforced, allowing a crafted page to exceed its authorized access boundaries. The affected component is Google Chrome desktop (all platforms) in versions prior to 150.0.7871.47, as confirmed by EUVD affected-version data ('Chrome 150.0.7871.47 < 150.0.7871.47'). The bug is tracked in Chromium's issue tracker at issues.chromium.org/issues/501810874, though full details may require authentication. The vulnerability is classified 'Low' severity by the Chromium security team, consistent with the constrained, sandbox-contained impact.
RemediationAI
The primary fix is upgrading Google Chrome to version 150.0.7871.47 or later via Chrome's built-in update mechanism or through enterprise management tooling; the stable channel advisory is at http://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. Patch availability is confirmed by the vendor; the exact fix version (150.0.7871.47) is independently corroborated by EUVD-2026-40739. Prior to patching in managed environments, organizations can reduce exposure by enforcing web content filtering policies to block navigation to untrusted or unknown sites, though this trades usability for risk reduction. Chrome Browser Cloud Management can be used to enforce update deadlines and restrict Chrome app/extension permissions as a compensating control. Given the low EPSS score and limited impact, this vulnerability should be remediated through normal patch cycles rather than emergency response.
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Moderate| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today