# CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes

> As of 2026-10-28, CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes) underlies 4 CVEs tracked by Threadlinqs, none of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 8 tracked threats.

**Last updated:** 2026-10-28

## What is CWE-915?

The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.

If the object contains attributes that were only intended for internal use, then their unexpected modification could lead to a vulnerability. This weakness is sometimes known by the language-specific mechanisms that make it possible, such as mass assignment, autobinding, or object injection.

CWE-915 is a base-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Language: Ruby; Language: ASP.NET; Language: PHP; Language: Python; Language: Not Language-Specific; Technology: Not Technology-Specific.

_Source: [MITRE CWE](https://cwe.mitre.org/data/definitions/915.html) (CWE-915 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data._

## Consequences

- **Integrity** — Modify Application Data. An attacker could modify sensitive data or program variables.
- **Integrity** — Execute Unauthorized Code or Commands
- **Other, Integrity** — Varies by Context, Alter Execution Logic

_Source: MITRE CWE, common consequences._

## How CWE-915 is exploited in the wild

Threadlinqs maps 4 CVEs to CWE-915, published between 2026-07-29 and 2026-10-24. None of them is in the CISA KEV catalog yet. By CVSS v3 severity the set splits into 1 critical, 3 high. The highest EPSS score in the set is 0.4% (CVE-2026-12436), the modelled probability of exploitation in the next 30 days. 8 tracked threats reference CWE-915 directly or through a CVE it covers; the most recent is “GitLab Patches 13 Security Flaws (incl. CVE-2026-6267, CVE-2026-12436) Enabling Data Exposure, CI/CD Tampering, and DoS” (2026-07-29). Affected products concentrate in GitLab (1), GitroomHQ (1), RARgames (1), among 4 vendors in total.

## Vulnerabilities (CVEs)

All 4 CVEs mapped to CWE-915, CISA KEV first, then by CVSS score.

- [CVE-2026-115933](https://intel.threadlinqs.com/cve/CVE-2026-115933) — CVSS 9.9 critical · EPSS 0.2% · published 2026-10-24
- [CVE-2026-71473](https://intel.threadlinqs.com/cve/CVE-2026-71473) — CVSS 8.5 high · EPSS 0.2% · published 2026-08-12
- [CVE-2026-12436](https://intel.threadlinqs.com/cve/CVE-2026-12436) — CVSS 8.4 high · EPSS 0.4% · published 2026-07-29
- [CVE-2026-53958](https://intel.threadlinqs.com/cve/CVE-2026-53958) — CVSS 7.6 high · EPSS 0.2% · published 2026-08-18

## Affected vendors

- [GitLab](https://intel.threadlinqs.com/vendors/gitlab) — 1 CVE
- **GitroomHQ** — 1 CVE
- **RARgames** — 1 CVE
- [Red Hat](https://intel.threadlinqs.com/vendors/red-hat) — 1 CVE

## Threat activity

8 tracked threats cite CWE-915:

- [GitLab Patches 13 Security Flaws (incl. CVE-2026-6267, CVE-2026-12436) Enabling Data Exposure, CI/CD Tampering, and DoS](https://intel.threadlinqs.com/threat/TL-2026-1806) — HIGH · 2026-07-29
- [ChromaDB CVE-2026-45829 "ChromaToast" — Pre-Auth RCE via trust_remote_code Hugging Face Model Load in FastAPI Server (HiddenLayer)](https://intel.threadlinqs.com/threat/TL-2026-0544) — CRITICAL · 2026-05-21
- [Leaked Shai-Hulud Source Code Fuels New npm Infostealer + DDoS Botnet Campaign (deadcode09284814, May 2026)](https://intel.threadlinqs.com/threat/TL-2026-0528) — HIGH · 2026-05-18
- [Microsoft Semantic Kernel — Critical RCE & Arbitrary File Write Chain (CVE-2026-26030, CVE-2026-25592)](https://intel.threadlinqs.com/threat/TL-2026-0481) — CRITICAL · 2026-05-08
- [SAP CAP & Cloud MTA npm Packages Compromised — Mini Shai-Hulud (TeamPCP) Bun-Based Credential Stealer](https://intel.threadlinqs.com/threat/TL-2026-0439) — CRITICAL · 2026-04-30
- [Bitwarden CLI npm Supply Chain Compromise (@bitwarden/cli v2026.4.0) — Shai-Hulud: The Third Coming / TeamPCP](https://intel.threadlinqs.com/threat/TL-2026-0429) — CRITICAL · 2026-04-27
- [GlassWorm v2 — 73 Open VSX Sleeper Extensions Activate Supply Chain Malware Against VS Code, Cursor, Windsurf and VSCodium Developers](https://intel.threadlinqs.com/threat/TL-2026-0421) — CRITICAL · 2026-04-24
- [Critical Protobuf.js Prototype Pollution Enables Remote Code Execution in Node.js Services (CVE-2026-44291)](https://intel.threadlinqs.com/threat/TL-2026-0392) — CRITICAL · 2026-04-19

## Mitigations

- **Implementation**: If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists. For applications written with Ruby on Rails, use the attr_accessible (allowlist) or attr_protected (denylist) macros in each class that may be used in mass assignment.
- **Architecture and Design, Implementation**: If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- **Implementation / Input Validation**: For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.
- **Implementation, Architecture and Design / Refactoring**: Refactor the code so that object attributes or fields do not need to be dynamically identified, and only expose getter/setter functionality for the intended attributes.

_Source: MITRE CWE, potential mitigations._

## Detection methods (MITRE CWE)

- **Automated Static Analysis** (effectiveness: High): 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.)

_Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher._

## Related weaknesses

- [CWE-913 Improper Control of Dynamically-Managed Code Resources](https://intel.threadlinqs.com/cwe/CWE-913)
- [CWE-502 Deserialization of Untrusted Data](https://intel.threadlinqs.com/cwe/CWE-502)

Canonical: https://intel.threadlinqs.com/cwe/CWE-915
Source definition: https://cwe.mitre.org/data/definitions/915.html
Detection rules and IOCs for threats exploiting CWE-915 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp
