CWE-427: Uncontrolled Search Path Element
Also known as: DLL preloading, Binary planting, Insecure library loading, Dependency confusion
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.
Last updated
Overview
Although this weakness can occur with any type of resource, it is frequently introduced when a product uses a directory search path to find executables or code libraries, but the path contains a directory that can be modified by an attacker, such as "/tmp" or the current working directory. In Windows-based systems, when the LoadLibrary or LoadLibraryEx function is called with a DLL name that does not contain a fully qualified path, the function follows a search order that includes two path elements that might be uncontrolled: the directory from which the program has been loaded the current working directory In some cases, the attack can be conducted remotely, such as when SMB or WebDAV network shares are used. One or more locations in that path could include the Windows drive root or its subdirectories. This often exists in Linux-based code assuming the controlled nature of the root directory (/) or its subdirectories (/etc, etc), or a code that recursively accesses the parent directory. In Windows, the drive root and some of its subdirectories have weak permissions by default, which makes them uncontrolled. In some Unix-based systems, a PATH might be created that contains an empty element, e.g. by splicing an empty variable into the PATH. This empty element can be interpreted as equivalent to the current working directory, which might be an untrusted search element. In software package management frameworks (e.g., npm, RubyGems, or PyPi), the framework may identify dependencies on third-party libraries or other packages, then consult a repository that contains the desired package. The framework may search a public repository before a private repository. This could be exploited by attackers by placing a malicious package in the public repository that has the same name as a package from the private repository. The search path might not be directly under control of the developer relying on the framework, but this search order effectively contains an untrusted element.
Real-world CVEs
860 recorded CVEs are caused by CWE-427 (Uncontrolled Search Path Element), including 2 in CISA's KEV (Known Exploited Vulnerabilities) catalog. KEVs are shown first. 163 new CWE-427 CVEs have been recorded so far in 2026 (218 in 2025).
- CVE-2020-3433CISA KEV
Cisco AnyConnect Secure Mobility Client for Windows DLL Hijacking Vulnerability
High · CVSS 8.5 · EPSS 95th2020-08-17 - CVE-2020-3153CISA KEV
Cisco AnyConnect Secure Mobility Client for Windows Uncontrolled Search Path Vulnerability
Medium · CVSS 6.0 · EPSS 98th2020-02-19 - CVE-2026-65093Critical · CVSS 9.9 · EPSS 40th2026-08-25
- CVE-2026-16860
IBM i is Affected By Remote Code Execution Vulnerability []
Critical · CVSS 9.9 · EPSS 42th2026-08-12 - CVE-2026-22619Critical · CVSS 9.9 · EPSS 25th2026-04-16
- CVE-2025-4981
Path Traversal Leading to RCE by Any Authenticated Mattermost User
Critical · CVSS 9.9 · EPSS 52th2025-06-20 - CVE-2025-69599Critical · CVSS 9.8 · EPSS 32th2026-05-08
- CVE-2025-65741Critical · CVSS 9.8 · EPSS 42th2025-12-09
- CVE-2024-42191
HCL Traveler for Microsoft Outlook (HTMO) is susceptible to COM hijacking
Critical · CVSS 9.8 · EPSS 16th2025-05-30 - CVE-2024-42190
HCL Traveler for Microsoft Outlook (HTMO) is susceptible to DLL hijacking
Critical · CVSS 9.8 · EPSS 16th2025-05-30 - CVE-2024-23054Critical · CVSS 9.8 · EPSS 68th2024-02-05
- CVE-2023-41117Critical · CVSS 9.8 · EPSS 53th2023-12-12
Showing 12 of 860 recorded CWE-427 CVEs. Track new ones as they are published and get AI-written analysis and fixes.
Monitor CWE-427 vulnerabilitiesCommon consequences
What can happen when CWE-427 is exploited.
Execute Unauthorized Code or Commands
Affects: Confidentiality, Integrity, Availability
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
How to prevent it
Practical mitigations for CWE-427, grouped by where in the lifecycle they apply.
Hard-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.
When 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 refer to these paths.
Remove 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.
Check 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.
Use 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.
How to detect it
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Effectiveness: High
Code examples
Illustrative examples from MITRE showing how the weakness appears in code.
The following code is from a web application that allows users access to an interface through which they can update their password on the system. In this environment, user passwords can be managed using the Network Information System (NIS), which is commonly used on UNIX systems. When performing NIS updates, part of the process for updating passwords is to run a make command in the /var/yp directory. Performing NIS updates requires extra privileges.
The problem here is that the program does not specify an absolute path for make and does not clean its environment prior to executing the call to Runtime.exec(). If an attacker can modify the $PATH variable to point to a malicious binary called make and cause the program to be executed in their environment, then the malicious binary will be loaded instead of the one intended. Because of the nature of the application, it runs with the privileges necessary to perform system operations, which means the attacker's make will now be run with these privileges, possibly giving the attacker complete control of the system.
In versions of Go prior to v1.19, the LookPath function would follow the conventions of the runtime OS and look for a program in the directiories listed in the current path [REF-1325].
Vulnerable example
func ExecuteGitCommand(name string, arg []string) error {In February 2021 [REF-1169], a researcher was able to demonstrate the ability to breach major technology companies by using "dependency confusion" where the companies would download and execute untrusted packages.
The researcher discovered the names of some internal, private packages by looking at dependency lists in public source code, such as package.json. The researcher then created new, untrusted packages with the same name as the internal packages, then uploaded them to package hosting services. These services included the npm registry for Node, PyPi for Python, and RubyGems. In affected companies, their dependency resolution would search the public hosting services first before consulting their internal service, causing the untrusted packages to be automatically downloaded and executed.
Illustrative examples
Real CVEs that MITRE cites as examples of this weakness.
- CVE-2023-25815 — chain: a change in an underlying package causes the gettext function to use implicit initialization with a hard-coded path (CWE-1419) under the user-writable C:\ drive, introducing an untrusted search path element (CWE-427) that enables spoofing of messages.
- CVE-2022-4826 — Go-based git extension on Windows can search for and execute a malicious "..exe" in a repository because Go searches the current working directory if git.exe is not found in the PATH
- CVE-2020-26284 — A Static Site Generator built in Go, when running on Windows, searches the current working directory for a command, possibly allowing code execution using a malicious .exe or .bat file with the name being searched
- CVE-2022-24765 — Windows-based fork of git creates a ".git" folder in the C: drive, allowing local attackers to create a .git folder with a malicious config file
- CVE-2019-1552 — SSL package searches under "C:/usr/local" for configuration files and other critical data, but C:/usr/local might be world-writable.
- CVE-2010-3402 — "DLL hijacking" issue in document editor.
- CVE-2010-3397 — "DLL hijacking" issue in encryption software.
- CVE-2010-3138 — "DLL hijacking" issue in library used by multiple media players.
- CVE-2010-3152 — "DLL hijacking" issue in illustration program.
- CVE-2010-3147 — "DLL hijacking" issue in address book.
- CVE-2010-3135 — "DLL hijacking" issue in network monitoring software.
- CVE-2010-3131 — "DLL hijacking" issue in web browser.
- CVE-2010-1795 — "DLL hijacking" issue in music player/organizer.
- CVE-2002-1576 — Product uses the current working directory to find and execute a program, which allows local users to gain privileges by creating a symlink that points to a malicious version of the program.
- CVE-1999-1461 — Product trusts the PATH environmental variable to find and execute a program, which allows local users to obtain root access by modifying the PATH to point to a malicous version of that program.
- CVE-1999-1318 — Software uses a search path that includes the current working directory (.), which allows local users to gain privileges via malicious programs.
- CVE-2003-0579 — Admin software trusts the user-supplied -uv.install command line option to find and execute the uv.install program, which allows local users to gain privileges by providing a pathname that is under control of the user.
- CVE-2000-0854 — When a document is opened, the directory of that document is first used to locate DLLs , which could allow an attacker to execute arbitrary commands by inserting malicious DLLs into the same directory as the document.
- CVE-2001-0943 — Database trusts the PATH environment variable to find and execute programs, which allows local users to modify the PATH to point to malicious programs.
- CVE-2001-0942 — Database uses an environment variable to find and execute a program, which allows local users to execute arbitrary programs by changing the environment variable.
- CVE-2001-0507 — Server uses relative paths to find system files that will run in-process, which allows local users to gain privileges via a malicious file.
- CVE-2002-2017 — Product allows local users to execute arbitrary code by setting an environment variable to reference a malicious program.
- CVE-1999-0690 — Product includes the current directory in root's PATH variable.
- CVE-2001-0912 — Error during packaging causes product to include a hard-coded, non-standard directory in search path.
- CVE-2001-0289 — Product searches current working directory for configuration file.
- CVE-2005-1705 — Product searches current working directory for configuration file.
- CVE-2005-1307 — Product executable other program from current working directory.
- CVE-2002-2040 — Untrusted path.
- CVE-2005-2072 — Modification of trusted environment variable leads to untrusted path vulnerability.
- CVE-2005-1632 — Product searches /tmp for modules before other paths.
Terminology & mappings
Alternate terms
- DLL preloading
- This term is one of several that are used to describe exploitation of untrusted search path elements in Windows systems, which received wide attention in August 2010. From a weakness perspective, the term is imprecise because it can apply to both CWE-426 and CWE-427.
- Binary planting
- This term is one of several that are used to describe exploitation of untrusted search path elements in Windows systems, which received wide attention in August 2010. From a weakness perspective, the term is imprecise because it can apply to both CWE-426 and CWE-427.
- Insecure library loading
- This term is one of several that are used to describe exploitation of untrusted search path elements in Windows systems, which received wide attention in August 2010. From a weakness perspective, the term is imprecise because it can apply to both CWE-426 and CWE-427.
- Dependency confusion
- As of February 2021, this term is used to describe CWE-427 in the context of managing installation of software package dependencies, in which attackers release packages on public sites where the names are the same as package names used by private repositories, and the search for the dependent package tries the public site first, downloading untrusted code. It may also be referred to as a "substitution attack."
Mapped taxonomies
- PLOVER: Uncontrolled Search Path Element
Attack patterns
CAPEC attack patterns that exploit this weakness.
Frequently asked questions
Common questions about CWE-427.
- What is CWE-427?
- 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.
- What CVEs are caused by CWE-427?
- 860 recorded CVEs are attributed to CWE-427, including CVE-2020-3433, CVE-2020-3153, CVE-2026-65093. 2 are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
- How do you prevent CWE-427?
- Hard-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.
- How is CWE-427 detected?
- Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
- What are the consequences of CWE-427?
- Exploiting CWE-427 can lead to: Execute Unauthorized Code or Commands.
- Is CWE-427 actively exploited?
- Yes. 2 CWE-427 vulnerabilities are in CISA's KEV catalog of actively exploited flaws, out of 860 recorded CVEs.
References
- MITRE CWE definition (CWE-427) (opens in a new tab)
- CWE-427 vulnerabilities on NVD (opens in a new tab)
- Learn: What is a CWE?
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Stay ahead of CWE-427
Get alerted the moment a new CWE-427 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.