Security Resilience

CWE · MITRE source

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Abstraction: Base · CVEs in our corpus: 10,693

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Many file operations are intended to take place within a restricted directory. By using special elements such as ".." and "/" separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the "../" sequence, which in most modern operating systems is interpreted as the parent directory of the current location. This is referred to as relative path traversal. Path traversal also covers the use of absolute pathnames such as "/usr/local/bin" to access unexpected files. This is referred to as absolute path traversal.

Last updated: 16 October 2026 07:24 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: partial · 1 mapping(s) from 1 framework(s): CSF 2.0 1 (partial)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A01:2025 Broken Access Control.

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • SI-10 Information Input Validation
  • PR.AA-05
  • PR.PS-02
  • SI-10 Information Input Validation
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)

—

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

NIST 800-53 r5 controls PROPOSED for this weakness (1)AI-assisted

These are model PROPOSALS, not graded mappings. They come from controls_to_cwe_proposals, which carries no grade field at all; across the CWE pages 1,540 of 1,722 such associations (89%) have never been graded by anything. The heading said “address” until 2026-09-29, which asserted a relationship the data does not carry. Graded cross-walks are on the framework map, not here.

Control Title Family Why it addresses this CWE
SI-10Information Input ValidationSIgraded mostly Validates pathnames and filenames to prevent traversal outside intended directories.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2019-11510 KEV 10.010.01.00002019-05-08
CVE-2021-41277 KEV 10.010.00.97182021-11-17
CVE-2025-34028 KEV 10.010.00.97602025-04-22
CVE-2026-34909 KEV 10.010.00.01792026-05-22
CVE-2026-48282 KEV 10.010.00.42392026-06-30
CVE-2004-0847 9.99.80.75702004-11-03
CVE-2010-2861 KEV 9.99.80.99752010-08-11
CVE-2014-0780 KEV 9.99.80.74682014-04-25
CVE-2016-6600 9.99.80.90802017-01-23
CVE-2016-7552 9.99.80.93252017-04-12
CVE-2015-9266 9.99.80.74002018-09-05
CVE-2019-3396 KEV 9.99.80.99912019-03-25
CVE-2019-12314 9.99.80.84222019-05-24
CVE-2019-1620 9.99.80.83782019-06-27
CVE-2019-16278 KEV 9.99.80.99032019-10-14
CVE-2019-17662 9.99.80.96762019-10-16
CVE-2019-7194 KEV 9.99.80.83122019-12-05
CVE-2019-7195 KEV 9.99.80.89542019-12-05
CVE-2019-19781 KEV 9.99.81.00002019-12-27
CVE-2014-8741 9.99.80.77202020-01-27
CVE-2020-6754 9.99.80.94802020-02-05
CVE-2020-11455 9.99.80.97182020-04-01
CVE-2020-3247 9.99.80.75572020-04-15
CVE-2020-3248 9.99.80.74442020-04-15
CVE-2020-5902 KEV 9.99.81.00002020-07-01