Threadlinqs IntelligenceStart free

Weakness · ClassCWE-74

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Likelihood of exploit: HighKEV-linkedClass

As of 2026-11-19, CWE-74 (Injection) underlies 95 CVEs tracked by Threadlinqs, 3 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 34 tracked threats. MITRE rates its likelihood of exploit as High.

CVEs
95Mapped to CWE-74
CISA KEV
3Exploited in the wild
Critical
15CVSS v3 critical CVEs
Threats
34Tracked campaigns citing it
Likelihood
HighMITRE likelihood of exploit

Last updated:

What is CWE-74?

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

CWE-74 is a class-level weakness in MITRE’s Common Weakness Enumeration, with a MITRE likelihood of exploit of High. Applicable platforms: Language: Not Language-Specific.

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

Consequences

  • Confidentiality — Read Application Data. Many injection attacks involve the disclosure of important information -- in terms of both data sensitivity and usefulness in further exploitation.
  • Access Control — Bypass Protection Mechanism. In some cases, injectable code controls authentication; this may lead to a remote vulnerability.
  • Other — Alter Execution Logic. Injection attacks are characterized by the ability to significantly change the flow of a given process, and in some cases, to the execution of arbitrary code.
  • Integrity, Other — Other. Data injection attacks lead to loss of data integrity in nearly all cases as the control-plane data injected is always incidental to data recall or writing.
  • Non-Repudiation — Hide Activities. Often the actions performed by injected control code are unlogged.

Source: MITRE CWE, common consequences.

How CWE-74 is exploited in the wild

Threadlinqs maps 95 CVEs to CWE-74, published between 2019-12-30 and 2026-11-15. 3 are listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild, and 1 is tied to ransomware campaigns. By CVSS v3 severity the set splits into 15 critical, 52 high, 26 medium. The highest EPSS score in the set is 99.9% (CVE-2023-22527), the modelled probability of exploitation in the next 30 days. 34 tracked threats reference CWE-74 directly or through a CVE it covers; the most recent is “Cron-Based Persistence on Network Appliances: Evooo1Bot and SSHStalker Linux Botnets” (2026-11-17). Affected products concentrate in SourceCodester (18), itsourcecode (11), code-projects (10), among 44 vendors in total.

Vulnerabilities (CVEs)

Showing 40 of 95 CVEs mapped to CWE-74, CISA KEV first, then by CVSS score.

  • CVE-2023-22527 — CISA KEV · CVSS 9.8 critical · EPSS 99.9% · published 2024-01-16
  • CVE-2022-35914 — CISA KEV · CVSS 9.8 critical · EPSS 99.8% · published 2022-09-19
  • CVE-2019-17558 — CISA KEV · CVSS 7.5 high · EPSS 98.5% · published 2019-12-30
  • CVE-2026-82971 — CVSS 10 critical · EPSS 1.8% · published 2026-08-31
  • CVE-2026-83524 — CVSS 9.9 critical · EPSS 1.6% · published 2026-08-31
  • CVE-2026-112371 — CVSS 9.9 critical · EPSS 0.4% · published 2026-10-19
  • CVE-2026-18684 — CVSS 9.8 critical · EPSS 2.0% · published 2026-08-03
  • CVE-2026-76473 — CVSS 9.8 critical · EPSS 0.4% · published 2026-10-21
  • CVE-2026-65669 — CVSS 9.6 critical · EPSS 0.8% · published 2026-09-08
  • CVE-2026-87701 — CVSS 9.6 critical · EPSS 0.4% · published 2026-09-17
  • CVE-2025-32711 — CVSS 9.3 critical · EPSS 8.0% · published 2025-06-11
  • CVE-2026-31816 — CVSS 9.1 critical · EPSS 16.6% · published 2026-03-09
  • CVE-2026-101261 — CVSS 9.1 critical · EPSS 2.3% · published 2026-09-28
  • CVE-2026-101262 — CVSS 9.1 critical · EPSS 2.3% · published 2026-09-28
  • CVE-2026-101260 — CVSS 9.1 critical · EPSS 2.3% · published 2026-09-28
  • CVE-2026-102792 — CVSS 9.1 critical · published 2026-09-29
  • CVE-2026-76472 — CVSS 8.8 high · EPSS 0.1% · published 2026-10-07
  • CVE-2026-79912 — CVSS 8.3 high · EPSS 1.4% · published 2026-08-25
  • CVE-2024-10914 — CVSS 8.1 high · EPSS 96.2% · published 2024-11-06
  • CVE-2024-10915 — CVSS 8.1 high · EPSS 79.6% · published 2024-11-06
  • CVE-2026-50107 — CVSS 8.1 high · EPSS 0.4% · published 2026-06-17
  • CVE-2026-71320 — CVSS 8.1 high · EPSS 0.4% · published 2026-08-05
  • CVE-2026-19960 — CVSS 7.4 high · EPSS 1.1% · published 2026-08-16
  • CVE-2026-78141 — CVSS 7.4 high · EPSS 1.0% · published 2026-08-23
  • CVE-2025-10123 — CVSS 7.3 high · EPSS 4.7% · published 2025-09-09
  • CVE-2026-115969 — CVSS 7.3 high · EPSS 1.3% · published 2026-10-24
  • CVE-2026-79845 — CVSS 7.3 high · EPSS 0.4% · published 2026-08-25
  • CVE-2026-14652 — CVSS 7.3 high · EPSS 0.4% · published 2026-07-04
  • CVE-2026-14653 — CVSS 7.3 high · EPSS 0.4% · published 2026-07-04
  • CVE-2026-14654 — CVSS 7.3 high · EPSS 0.4% · published 2026-07-04
  • CVE-2026-14660 — CVSS 7.3 high · EPSS 0.4% · published 2026-07-04
  • CVE-2026-95819 — CVSS 7.3 high · EPSS 0.4% · published 2026-09-22
  • CVE-2026-14648 — CVSS 7.3 high · EPSS 0.3% · published 2026-07-04
  • CVE-2026-105469 — CVSS 7.3 high · EPSS 0.3% · published 2026-10-05
  • CVE-2026-13500 — CVSS 7.3 high · EPSS 0.3% · published 2026-06-28
  • CVE-2026-115970 — CVSS 7.3 high · EPSS 0.3% · published 2026-10-24
  • CVE-2026-105166 — CVSS 7.3 high · EPSS 0.2% · published 2026-10-04
  • CVE-2026-105167 — CVSS 7.3 high · EPSS 0.2% · published 2026-10-04
  • CVE-2026-116060 — CVSS 7.3 high · EPSS 0.2% · published 2026-10-25
  • CVE-2026-116062 — CVSS 7.3 high · EPSS 0.2% · published 2026-10-25

Affected vendors

Threat activity

34 tracked threats cite CWE-74; the 25 most recent are listed.

Mitigations

  • Requirements: Programming languages and supporting technologies might be chosen which are not subject to these issues.
  • Implementation: Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.

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.