CWE · MITRE source
CWE-843Access of Resource Using Incompatible Type ('Type Confusion')
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.
Last updated: 15 October 2026 22:33 UTC
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2012-0507 KEV UPD | 9.9 | 9.8 | 0.9819 | 2012-06-07 |
CVE-2025-10585 KEV UPD | 9.9 | 9.8 | 0.0539 | 2025-09-24 |
CVE-2024-4947 KEV UPD | 9.4 | 9.6 | 0.1524 | 2024-05-15 |
CVE-2024-5274 KEV UPD | 9.4 | 9.6 | 0.0747 | 2024-05-28 |
CVE-2024-7971 KEV UPD | 9.4 | 9.6 | 0.2110 | 2024-08-21 |
CVE-2011-0611 KEV UPD | 9.2 | 8.8 | 0.9941 | 2011-04-13 |
CVE-2016-7201 KEV UPD | 9.2 | 8.8 | 0.8000 | 2016-11-10 |
CVE-2017-11292 KEV UPD | 9.2 | 8.8 | 0.1188 | 2017-10-22 |
CVE-2017-5070 KEV UPD | 9.2 | 8.8 | 0.3207 | 2017-10-27 |
CVE-2019-11707 KEV UPD | 9.2 | 8.8 | 0.3770 | 2019-07-23 |
CVE-2019-8506 KEV UPD | 9.2 | 8.8 | 0.1616 | 2019-12-18 |
CVE-2020-6418 KEV UPD | 9.2 | 8.8 | 0.7881 | 2020-02-27 |
CVE-2019-17026 KEV UPD | 9.2 | 8.8 | 0.4631 | 2020-03-02 |
CVE-2020-16009 KEV UPD | 9.2 | 8.8 | 0.4829 | 2020-11-03 |
CVE-2021-1789 KEV UPD | 9.2 | 8.8 | 0.1398 | 2021-04-02 |
CVE-2021-21224 KEV UPD | 9.2 | 8.8 | 0.8417 | 2021-04-26 |
CVE-2021-30551 KEV UPD | 9.2 | 8.8 | 0.6470 | 2021-06-15 |
CVE-2021-30563 KEV UPD | 9.2 | 8.8 | 0.0900 | 2021-08-03 |
CVE-2022-1096 KEV UPD | 9.2 | 8.8 | 0.2473 | 2022-07-23 |
CVE-2022-1364 KEV UPD | 9.2 | 8.8 | 0.1392 | 2022-07-26 |
CVE-2022-3723 KEV UPD | 9.2 | 8.8 | 0.0792 | 2022-11-01 |
CVE-2022-4262 KEV UPD | 9.2 | 8.8 | 0.2351 | 2022-12-02 |
CVE-2022-42856 KEV UPD | 9.2 | 8.8 | 0.0852 | 2022-12-15 |
CVE-2023-23529 KEV UPD | 9.2 | 8.8 | 0.0950 | 2023-02-27 |
CVE-2023-2033 KEV UPD | 9.2 | 8.8 | 0.4080 | 2023-04-14 |