CWE-669: Incorrect Resource Transfer Between Spheres
The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.
Last updated
Overview
CWE-669 (Incorrect Resource Transfer Between Spheres) is a class-level software weakness catalogued by MITRE in the Common Weakness Enumeration (CWE). It describes a recurring type of mistake that can lead to exploitable security vulnerabilities.
Background
A "control sphere" is a set of resources and behaviors that are accessible to a single actor, or a group of actors. A product's security model will typically define multiple spheres, possibly implicitly. For example, a server might define one sphere for "administrators" who can create new user accounts with subdirectories under /home/server/, and a second sphere might cover the set of users who can create or delete files within their own subdirectories. A third sphere might be "users who are authenticated to the operating system on which the product is installed." Each sphere has different sets of actors and allowable behaviors.
Real-world CVEs
112 recorded CVEs are caused by CWE-669 (Incorrect Resource Transfer Between Spheres), including 1 in CISA's KEV (Known Exploited Vulnerabilities) catalog. KEVs are shown first. 55 new CWE-669 CVEs have been recorded so far in 2026 (18 in 2025).
- CVE-2026-31431CISA KEV
crypto: algif_aead - Revert to operating out-of-place
High · CVSS 8.5 · EPSS 100th2026-04-22 - CVE-2021-30120
2FA bypass in Kaseya VSA <= v9.5.6
Critical · CVSS 9.9 · EPSS 93th2021-07-09 - CVE-2026-75003
In Roundcube Webmail before 1.6.18 and 1.7.x before 1.7.3, an unclosed url() in a FuncIRI...
Critical · CVSS 9.8 · EPSS 35th2026-08-17 - CVE-2025-67895
Apache Airflow Providers Edge3: Edge3 Worker RPC RCE on Airflow 2
Critical · CVSS 9.8 · EPSS 68th2025-12-17 - CVE-2020-5800Critical · CVSS 9.8 · EPSS 76th2020-12-07
- CVE-2020-15892Critical · CVSS 9.8 · EPSS 77th2020-07-22
- CVE-2016-5062Critical · CVSS 9.8 · EPSS 90th2016-09-29
- CVE-2026-20194
Cisco Identity Services Engine Hardening Release - Incorrect Resource Transfer Vulnerabilities
Critical · CVSS 9.1 · EPSS 42th2026-09-16 - CVE-2023-31114Critical · CVSS 9.1 · EPSS 47th2023-06-07
- CVE-2026-33265Critical · CVSS 9.0 · EPSS 14th2026-03-18
- CVE-2026-92952
vm2 3.11.4 through 3.11.6 Sandbox Symbol Filtering Bypass
High · CVSS 8.9 · EPSS 40th2026-09-17 - CVE-2025-41660
CODESYS Control Boot Application Replacement Enables Code Execution
High · CVSS 8.8 · EPSS 39th2026-03-24
Showing 12 of 112 recorded CWE-669 CVEs. Get an alert for each new one, with AI-written analysis and fixes.
Monitor these CVEsCommon consequences
What can happen when CWE-669 is exploited.
Read Application Data, Modify Application Data, Unexpected State
Affects: Confidentiality, Integrity
How it happens
When it is introduced
Typically introduced during these phases of the software lifecycle.
Code examples
MITRE examples of the weakness in code.
The following code demonstrates the unrestricted upload of a file with a Java servlet and a path traversal vulnerability. The action attribute of an HTML form is sending the upload file request to the Java servlet.
Vulnerable example
public class FileUploadServlet extends HttpServlet {
...
response.setContentType("text/html");
// extract the filename from the Http header
BufferedWriter bw = new BufferedWriter(new FileWriter(uploadLocation+filename, true));
if (line.indexOf(boundary) == -1) {
bw.write(line);
...This code includes an external script to get database credentials, then authenticates a user against the database, allowing access to the application.
Vulnerable example
//assume the password is already encrypted, avoiding CWE-312
//dbInfo.php makes $dbhost, $dbuser, $dbpass, $dbname available
mysql_close();
mysql_close();This code either generates a public HTML user information page or a JSON response containing the same user information.
Vulnerable example
// API flag, output JSON if set
$record = getUserRecord($username);
if($fieldName == "email_address") {
// skip displaying user emails
writeToHtmlPage($fieldName,$fieldValue);
$record = getUserRecord($username);The programmer is careful to not display the user's e-mail address when displaying the public HTML page. However, the e-mail address is not removed from the JSON response, exposing the user's e-mail address.
Illustrative examples
Real CVEs that MITRE cites as examples of this weakness.
- CVE-2021-22909 — Chain: router's firmware update procedure uses curl with "-k" (insecure) option that disables certificate validation (CWE-295), allowing adversary-in-the-middle (AITM) compromise with a malicious firmware image (CWE-494).
- CVE-2023-5227 — PHP-based FAQ management app does not check the MIME type for uploaded images
- CVE-2005-0406 — Some image editors modify a JPEG image, but the original EXIF thumbnail image is left intact within the JPEG. (Also an interaction error).
Frequently asked questions
Common questions about CWE-669.
- What is CWE-669?
- The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.
- What CVEs are caused by CWE-669?
- 112 recorded CVEs are attributed to CWE-669, including CVE-2026-31431, CVE-2021-30120 and CVE-2026-75003. 1 is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog.
- What are the consequences of CWE-669?
- Exploiting CWE-669 can lead to: Read Application Data, Modify Application Data, Unexpected State.
- Is CWE-669 actively exploited?
- Yes. 1 CWE-669 vulnerability is in CISA's KEV catalog of actively exploited flaws, out of 112 recorded CVEs.
References
- MITRE CWE definition (CWE-669) (opens in a new tab)
- CWE-669 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.
Track CWE-669 CVEs
Get an alert when a new CWE-669 CVE affects your products, with AI-written analysis and remediation steps.