CWE•Base•Draft•20 recent CVEs
CWE-427Uncontrolled Search Path Element
Description
The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.
[object Object]
Common consequences
- Confidentiality,Integrity,Availability→Execute Unauthorized Code or Commands
Potential mitigations
- Architecture and Design,ImplementationHard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.
- ImplementationWhen invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames. The portability can be improved by locating the full-qualified paths in a centralized, easily-modifiable location within the source code, and having the code ref
- ImplementationRemove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.
- ImplementationCheck your search path before use and remove any elements that are likely to be unsafe, such as the current working directory or a temporary files directory. Since this is a denylist approach, it might not be a complete solution.
- ImplementationUse other functions that require explicit paths. Making use of any of the other readily available functions that require explicit paths is a safe way to avoid this problem. For example, system() in C does not require a full path since the shell can take care of finding the program using the PATH environment variable, while execl() and execv() require a full path.
Related CWEs
Recent CVEs classified under this CWE
CVE-2026-877908.82026-11-18CVE-2026-1013277.82026-11-16CVE-2026-672507.32026-11-16CVE-2026-157072026-11-16CVE-2026-1281347.82026-11-13CVE-2026-96617.02026-11-13CVE-2026-64677.22026-11-12CVE-2026-1266077.82026-11-11CVE-2026-406262026-11-10CVE-2026-578842026-11-10CVE-2026-564382026-11-10CVE-2026-466322026-11-10CVE-2026-207982026-11-10CVE-2026-90636.72026-11-10CVE-2026-865798.22026-11-10CVE-2026-1200157.52026-11-10CVE-2026-1140327.82026-11-09CVE-2026-1049892026-11-09CVE-2026-1121702026-11-09CVE-2026-1184502026-11-09