Threadlinqs IntelligenceStart free

Weakness · ClassCWE-913

CWE-913: Improper Control of Dynamically-Managed Code Resources

KEV-linkedClass

As of 2026-10-14, CWE-913 (Improper Control of Dynamically-Managed Code Resources) underlies 4 CVEs tracked by Threadlinqs, 1 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 16 tracked threats.

CVEs
4Mapped to CWE-913
CISA KEV
1Exploited in the wild
Critical
2CVSS v3 critical CVEs
Threats
16Tracked campaigns citing it
Likelihood
—MITRE likelihood of exploit

Last updated:

What is CWE-913?

The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.

Many languages offer powerful features that allow the programmer to dynamically create or modify existing code, or resources used by code such as variables and objects. While these features can offer significant flexibility and reduce development time, they can be extremely dangerous if attackers can directly influence these code resources in unexpected ways.

CWE-913 is a class-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Language: Not Language-Specific; Language: Interpreted.

Source: MITRE CWE (CWE-913 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.

Consequences

  • Integrity — Execute Unauthorized Code or Commands
  • Other, Integrity — Varies by Context, Alter Execution Logic

Source: MITRE CWE, common consequences.

How CWE-913 is exploited in the wild

Threadlinqs maps 4 CVEs to CWE-913, published between 2021-03-30 and 2026-10-08. 1 is listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild. By CVSS v3 severity the set splits into 2 critical, 1 high. The highest EPSS score in the set is 98.9% (CVE-2025-68613), the modelled probability of exploitation in the next 30 days. 16 tracked threats reference CWE-913 directly or through a CVE it covers; the most recent is “CVE-2026-103663: Ollama /api/pull path traversal (digestToPath) enables unauthenticated remote file write and root RCE” (2026-10-08). Affected products concentrate in N8n (2), Ollama (1), laverdet (1).

Vulnerabilities (CVEs)

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

Affected vendors

  • N8n — 2 CVEs
  • Ollama — 1 CVE
  • laverdet — 1 CVE

Threat activity

16 tracked threats cite CWE-913:

Mitigations

  • Implementation / Input Validation: For any externally-influenced input, check the input against an allowlist of acceptable values.
  • Implementation, Architecture and Design / Refactoring: Refactor the code so that it does not need to be dynamically managed.

Source: MITRE CWE, potential mitigations.

Detection methods (MITRE CWE)

  • Fuzzing (effectiveness: High): Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.

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