CVE-2025-1915: Google Chrome · Improper Limitation of a Pathname to a Restricted Directory
Affects Google ChromeSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 134.0.6998.35 soon.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 134.0.6998.35
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Google Chrome to 134.0.6998.35.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | Affected
| Fixed in
|
AI-suggested
- Immediately update Google Chrome to version 134.0.6998.35 or later, where the vulnerability is patched.
- Implement strict policies to control and limit the installation of Chrome extensions, especially from untrusted sources.
- Educate users about the risks of installing extensions and encourage verification of extension authenticity.
- Employ endpoint security solutions that monitor and restrict unauthorized file access by browser extensions.
- Regularly audit installed extensions and remove any that are unnecessary or suspicious.
- Use enterprise management tools to enforce extension whitelisting and prevent sideloading of unapproved extensions.
- Monitor network and system logs for unusual file access patterns that may indicate exploitation attempts.
Description
Improper Limitation of a Pathname to a Restricted Directory in DevTools in Google Chrome on Windows prior to 134.0.6998.35 allowed an attacker who convinced a user to install a malicious extension to bypass file access restrictions via a crafted Chrome Extension. (Chromium security severity: Medium)