Skip to content
Insights · weakness

CWE-73: External Control of File Name or Path

Sources read 2026-11-18. MITRE's own page · All weakness notes · Added to CISA's list in the last seven days

What it is

From MITRE's CWE catalogue

The product allows user input to control or influence paths or file names that are used in filesystem operations.

MITRE classes it as a base-level weakness and rates the likelihood of exploit as high.

What it lets an attacker do

From MITRE's CWE catalogue

  • Read Files or Directories (affects: integrity, confidentiality)
  • Modify Files or Directories, Execute Unauthorized Code or Commands (affects: integrity, confidentiality, availability)
  • DoS: Crash, Exit, or Restart, DoS: Resource Consumption (Other) (affects: availability)

On CISA's exploited list

From CISA's exploited list

2 of the 113 entries CISA added from 2026-08-21 to 2026-11-18 name CWE-73, against 0 of 71 in the 90 days before. Over the whole catalogue 7 entries name it. The counts are small, so read them as a rough order, not a rate.

CISA's list is not every flaw that is exploited: it holds the ones CISA has evidence of, listed on the day it added them.

  • CVE-2026-90817, Vanderbilt University Research Electronic Data Capture (REDCap), added 2026-11-18
  • CVE-2026-96656, Plex Media Server, added 2026-10-20
  • CVE-2025-33053, Microsoft Windows, added 2025-06-10
  • CVE-2025-24054, Microsoft Windows, added 2025-04-17
  • CVE-2025-0111, Palo Alto Networks PAN-OS, added 2025-02-20

How MITRE says to find it

From MITRE's CWE catalogue

  • Automated Static Analysis

What MITRE suggests

From MITRE's CWE catalogue

These are MITRE's suggestions, quoted as it gives them. They are not a complete fix and not a substitute for reading the vendor's advisory for the product you run.

  • Architecture and Design: When the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt".
  • Architecture and Design: Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory. Examples include the Unix chroot jail and AppArmor.
  • Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602.
  • Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.

Attack patterns MITRE links to it

From MITRE's CWE catalogue

Start with one piece of work.

Give us one piece of work and read access to one system. We map it and come back with what we found, what we would build and what it would take — before any commitment. You decide using our output, not our pitch.

Talk to us