CWE-829: Inclusion of Functionality from Untrusted Control Sphere
315 CVEs have CWE-829 as their primary weakness. 3 of them are in the CISA KEV catalog. The highest EPSS score among them is 62.562%.
The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.
Child of CWE-669: Incorrect Resource Transfer Between Spheres
Mitigations
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
- Architecture and Design: When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs. For example, ID 1 could map to inbox.txt and ID 2 could map to profile.txt. Features such as the ESAPI AccessReferenceMap [REF-45] provide this capability.
- 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. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Architecture and Design Operation: Run the code in a jail or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software. OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.
- Architecture and Design Operation: Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
- 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. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, boat may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as red or blue. Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However,…
- Architecture and Design Operation: Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately. This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.
- Architecture and Design Implementation: Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls. Many file inclusion problems occur because the programmer assumed that certain inputs could not be modified, especially for cookies and URL components.
- Operation: Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
Observed examples
- CVE-2010-2076: Product does not properly reject DTDs in SOAP messages, which allows remote attackers to read arbitrary files, send HTTP requests to intranet servers, or cause a denial of service.
- CVE-2004-0285: Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.
- CVE-2004-0030: Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.
- CVE-2004-0068: Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.
- CVE-2005-2157: Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.
- CVE-2005-2162: Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.
- CVE-2005-2198: Modification of assumed-immutable configuration variable in include file allows file inclusion via direct request.
- CVE-2004-0128: Modification of assumed-immutable variable in configuration script leads to file inclusion.
- CVE-2005-1864: PHP file inclusion.
- CVE-2005-1869: PHP file inclusion.
- CVE-2005-1870: PHP file inclusion.
- CVE-2005-2154: PHP local file inclusion.
- CVE-2002-1704: PHP remote file include.
- CVE-2002-1707: PHP remote file include.
- CVE-2005-1964: PHP remote file include.
- CVE-2005-1681: PHP remote file include.
- CVE-2005-2086: PHP remote file include.
- CVE-2004-0127: Directory traversal vulnerability in PHP include statement.
- CVE-2005-1971: Directory traversal vulnerability in PHP include statement.
- CVE-2005-3335: PHP file inclusion issue, both remote and local; local include uses .. and %00 characters as a manipulation, but many remote file inclusion issues probably have this vector.
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2026-0770 | 2026-01-23 | CRITICAL | 9.8 | 62.562% | Langflow exec_globals Inclusion of Functionality from Untrusted Control Sphere Remote Code Execution Vulnerability. This vulnerability allows remote attackers… |
| CVE-2025-32463 | 2025-06-30 | CRITICAL | 9.3 | 56.300% | Sudo before 1.9.17p1 allows local users to obtain root access because /etc/nsswitch.conf from a user-controlled directory is used with the --chroot option. |
| CVE-2026-111357 | 2026-10-15 | HIGH | 7.0 | 0.533% | Ivanti Connect Secure 22.8R2.4 mishandles the manner in which the dsinvoked broker trusts DSCache configuration data, leading to privilege escalation to root… |
| CVE-2026-104007 | 2026-11-16 | HIGH | 8.5 | 0.206% | LibreOffice can connect to databases through JDBC drivers written in Java. A spreadsheet can use a database as the source of a pivot table, and the database… |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-829'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-829'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).