CVE-2025-1915
Reported by chrome · Published March 5, 2025
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)
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| chromium | Wolfi | 134.0.6998.35-r0 |
| qt6-qtwebengine | Alpine | 6.8.2-r3 |
| chromium | Chainguard | 134.0.6998.35-r0 |
| chrome | 134.0.6998.35 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Chrome | 134.0.6998.35 | |
| Chrome | 134.0.6998.35 | |
| wolfi | chromium | 0 |
| alpine | qt6-qtwebengine | 0 |
| chainguard | chromium | 0 |
Timeline
- Mar 4, 2025 CVE Published
- Mar 5, 2025 EPSS Score (30 in total, the first dated here)
- Mar 6, 2025 Coalition ESS Score (11 in total, the first dated here)
- Apr 22, 2026 Security Advisory (13 in total, the first dated here)
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-1915
vulnetix vdb fixes CVE-2025-1915
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-1915/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart