Threadlinqs IntelligenceStart free

Weakness · BaseCWE-822

CWE-822: Untrusted Pointer Dereference

KEV-linkedBase

As of 2026-11-19, CWE-822 (Untrusted Pointer Dereference) underlies 24 CVEs tracked by Threadlinqs, 2 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 27 tracked threats.

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

Last updated:

What is CWE-822?

The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.

An attacker can supply a pointer for memory locations that the product is not expecting. If the pointer is dereferenced for a write operation, the attack might allow modification of critical state variables, cause a crash, or execute code. If the dereferencing operation is for a read, then the attack might allow reading of sensitive data, cause a crash, or set a variable to an unexpected value (since the value will be read from an unexpected memory location). There are several variants of this weakness, including but not necessarily limited to: The untrusted value is directly invoked as a function call. In OS kernels or drivers where there is a boundary between "userland" and privileged memory spaces, an untrusted pointer might enter through an API or system call (see CWE-781 for one such example). Inadvertently accepting the value from an untrusted control sphere when it did not have to be accepted as input at all. This might occur when the code was originally developed to be run by a single user in a non-networked environment, and the code is then ported to or otherwise exposed to a networked environment.

CWE-822 is a base-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Language: Memory-Unsafe; Language: C; Language: C++.

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

Consequences

  • Confidentiality — Read Memory. If the untrusted pointer is used in a read operation, an attacker might be able to read sensitive portions of memory.
  • Availability — DoS: Crash, Exit, or Restart. If the untrusted pointer references a memory location that is not accessible to the product, or points to a location that is "malformed" or larger than expected by a read or write operation, the application may terminate unexpectedly.
  • Integrity, Confidentiality, Availability — Execute Unauthorized Code or Commands, Modify Memory. If the untrusted pointer is used in a function call, or points to unexpected data in a write operation, then code execution may be possible.

Source: MITRE CWE, common consequences.

How CWE-822 is exploited in the wild

Threadlinqs maps 24 CVEs to CWE-822, published between 2023-01-10 and 2026-11-10. 2 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 1 critical, 17 high, 3 medium. The highest EPSS score in the set is 65.4% (CVE-2023-21768), the modelled probability of exploitation in the next 30 days. 27 tracked threats reference CWE-822 directly or through a CVE it covers; the most recent is “Microsoft Patch Tuesday November 2026: ~1,095 vulnerabilities, 64 critical, one exploited Outlook NTLM-leak spoofing zero-day (CVE-2026-124194)” (2026-11-11). Affected products concentrate in Microsoft (19), AMD (1), Autodesk (1), among 5 vendors in total.

Vulnerabilities (CVEs)

All 24 CVEs mapped to CWE-822, CISA KEV first, then by CVSS score.

Affected vendors

Threat activity

27 tracked threats cite CWE-822; the 25 most recent are listed.

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.)
  • Automated Dynamic Analysis (effectiveness: Moderate): Use tools that are integrated during compilation to insert runtime error-checking mechanisms related to memory safety errors, such as AddressSanitizer (ASan) for C/C++ [REF-1518].

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