Threadlinqs IntelligenceStart free

Weakness · BaseCWE-843

CWE-843: Access of Resource Using Incompatible Type ('Type Confusion')

KEV-linkedBase

As of 2026-10-05, CWE-843 (Type Confusion) underlies 22 CVEs tracked by Threadlinqs, 11 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 38 tracked threats.

CVEs
22Mapped to CWE-843
CISA KEV
11Exploited in the wild
Critical
2CVSS v3 critical CVEs
Threats
38Tracked campaigns citing it
Likelihood
—MITRE likelihood of exploit

Last updated:

What is CWE-843?

The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.

When the product accesses the resource using an incompatible type, this could trigger logical errors because the resource does not have expected properties. In languages without memory safety, such as C and C++, type confusion can lead to out-of-bounds memory access. While this weakness is frequently associated with unions when parsing data with many different embedded object types in C, it can be present in any application that can interpret the same variable or memory location in multiple ways. This weakness is not unique to C and C++. For example, errors in PHP applications can be triggered by providing array parameters when scalars are expected, or vice versa. Languages such as Perl, which perform automatic conversion of a variable of one type when it is accessed as if it were another type, can also contain these issues.

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

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

Consequences

  • Availability, Integrity, Confidentiality — Read Memory, Modify Memory, Execute Unauthorized Code or Commands, DoS: Crash, Exit, or Restart. When a memory buffer is accessed using the wrong type, it could read or write memory out of the bounds of the buffer, if the allocated buffer is smaller than the type that the code is attempting to access, leading to a crash and possibly code execution.

Source: MITRE CWE, common consequences.

How CWE-843 is exploited in the wild

Threadlinqs maps 22 CVEs to CWE-843, published between 2017-04-27 and 2026-09-29. 11 are 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, 19 high, 1 medium. The highest EPSS score in the set is 96.9% (CVE-2017-8291), the modelled probability of exploitation in the next 30 days. 38 tracked threats reference CWE-843 directly or through a CVE it covers; the most recent is “Google Chrome 154 Update Fixes 32 Security Flaws Including Critical ANGLE Buffer Overflow (CVE-2026-102331)” (2026-09-30). Affected products concentrate in Google (10), Microsoft (8), Apple (5), among 13 vendors in total.

Vulnerabilities (CVEs)

All 22 CVEs mapped to CWE-843, CISA KEV first, then by CVSS score.

  • CVE-2024-7971 — CISA KEV · CVSS 9.6 critical · EPSS 1.0% · published 2024-08-21
  • CVE-2023-4762 — CISA KEV · CVSS 8.8 high · EPSS 63.5% · published 2023-09-05
  • CVE-2023-2033 — CISA KEV · CVSS 8.8 high · EPSS 25.1% · published 2023-04-14
  • CVE-2023-3079 — CISA KEV · CVSS 8.8 high · EPSS 2.1% · published 2023-06-05
  • CVE-2026-85046 — CISA KEV · CVSS 8.8 high · EPSS 1.1% · published 2026-09-03
  • CVE-2024-23222 — CISA KEV · CVSS 8.8 high · EPSS 0.6% · published 2024-01-23
  • CVE-2022-42856 — CISA KEV · CVSS 8.8 high · EPSS 0.1% · published 2022-12-15
  • CVE-2023-23529 — CISA KEV · CVSS 8.8 high · EPSS 0.0% · published 2023-02-27
  • CVE-2025-6554 — CISA KEV · CVSS 8.1 high · EPSS 0.9% · published 2025-06-30
  • CVE-2017-8291 — CISA KEV · CVSS 7.8 high · EPSS 96.9% · published 2017-04-27
  • CVE-2026-21519 — CISA KEV · CVSS 7.8 high · EPSS 4.5% · published 2026-02-10
  • CVE-2026-22104 — CVSS 9.8 critical · EPSS 91.2% · published 2026-02-20
  • CVE-2026-102299 — CVSS 8.8 high · published 2026-09-29
  • CVE-2026-102323 — CVSS 8.8 high · published 2026-09-29
  • CVE-2026-14431 — CVSS 8.8 high · published 2026-07-01
  • CVE-2025-62554 — CVSS 8.4 high · EPSS 0.3% · published 2025-12-09
  • CVE-2026-40364 — CVSS 8.4 high · EPSS 0.1% · published 2026-05-12
  • CVE-2026-26110 — CVSS 8.4 high · EPSS 0.1% · published 2026-03-10
  • CVE-2026-33824 — CVSS 8.4 high · EPSS 0.0% · published 2026-04-14
  • CVE-2026-5946 — CVSS 7.5 high · EPSS 0.0% · published 2026-05-20
  • CVE-2026-9117 — CVSS 7.5 high · EPSS 0.0% · published 2026-05-20
  • CVE-2026-10702 — CVSS 4.3 medium · EPSS 0.5% · published 2026-06-02

Affected vendors

Threat activity

38 tracked threats cite CWE-843; 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.)

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