ChromeWeb browser · Google
CVE-2025-1915
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper 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)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePath traversal vulnerability in Chrome DevTools on Windows allowing a malicious extension to escape directory restrictions and access files outside the intended scope by bypassing file access controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 134.0.6998.35CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Chrome is installed on WindowsOpen Command Prompt and run: reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v DisplayName 2>nul OR check C:\Program Files\Google\Chrome\Application\chrome.exe existsAffected if Chrome is installed on the Windows system
-
Determine installed Chrome versionOpen Chrome, go to Settings > About Chrome, or run: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version in Command PromptAffected if The displayed version is lower than 134.0.6998.35
-
Check if Chrome extensions are installedOpen Chrome, navigate to chrome://extensions/ and review the list of installed extensionsAffected if Any extension is installed, especially from untrusted sources (the vulnerability requires a malicious extension)
-
Confirm DevTools accessibilityOpen any webpage in Chrome, right-click and select Inspect, or press F12 to confirm DevTools functionalityAffected if DevTools is functional (the vulnerability exists within DevTools on Windows)
A user is affected if they are running Google Chrome on Windows with a version lower than 134.0.6998.35 and have any extensions installed that could potentially exploit the DevTools path traversal flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped134.0.6998.35
Update Google Chrome to version 134.0.6998.35 or later. Avoid installing untrusted or malicious browser extensions.
134.0.6998.35 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Verify the current version number
- If version is below 134.0.6998.35, Chrome will automatically check for updates
- Click 'Update Google Chrome' if an update is available
- Restart Chrome to complete the update
- Alternatively, download the latest stable Chrome from chrome.com and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-1915 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data