Cyber Resilience

CVE-2025-1915

Path Traversal in Google Chrome ≤ 134.0.6998.35

Path Traversal
Published
05 March 2025
Modified
01 April 2025
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS Score 0.0040 33th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2025-1915 is a high-severity Path Traversal (CWE-22) vulnerability in Google Chrome. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-1915, published on 2025-03-05, is an Improper Limitation of a Pathname to a Restricted Directory vulnerability (CWE-22) in DevTools within Google Chrome on Windows versions prior to 134.0.6998.35. This flaw enables attackers to bypass file access restrictions through a crafted Chrome Extension. It carries a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N), classified as High severity, though Chromium rates it as Medium.

Exploitation requires an attacker to convince a targeted user to install a malicious Chrome extension, involving network access with low attack complexity and no required privileges, but necessitating user interaction. Upon success, the attacker achieves high impacts on confidentiality and integrity, allowing unauthorized access to restricted files, while availability remains unaffected.

Google's stable channel update for desktop, detailed at chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop.html, patches this issue in Chrome version 134.0.6998.35. Additional technical details are available in the Chromium issue tracker at issues.chromium.org/issues/391114799. Mitigation involves updating affected Windows installations to the latest stable Chrome release.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

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…

more

Extension. (Chromium security severity: Medium)

CWE(s)
CWE-22

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-24749Same product: Microsoft Windows
CVE-2024-7263Same product: Microsoft Windows
CVE-2025-63372Same product: Microsoft Windows
CVE-2025-11001Same product: Microsoft Windows
CVE-2024-42474Same product: Microsoft Windows
CVE-2023-41747Same product: Microsoft Windows
CVE-2019-18187Same product: Microsoft Windows
CVE-2023-4593Same product: Microsoft Windows
CVE-2026-32310Same product: Microsoft Windows
CVE-2024-7262Same product: Microsoft Windows

Affected Assets

google
chrome
≤ 134.0.6998.35

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Enforces the intended directory access authorizations that path traversal would otherwise bypass.

SI-10 Information Input Validation good match

Input validation directly neutralizes special path elements before pathname construction occurs.

AC-6 Least Privilege partial match

Least privilege reduces the impact of any unauthorized file access obtained via traversal.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches path traversal via static/dynamic analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for safe file handling and canonicalization.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles require least-privilege file access and directory isolation.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

A.8.3 Information access restriction partial match
mitigates

Information access restriction limits which files an application may read or write.

References