CWE · MITRE source
CWE-823Use of Out-of-range Pointer Offset
The product performs pointer arithmetic on a valid pointer, but it uses an offset that can point outside of the intended range of valid memory locations for the resulting pointer.
While a pointer can contain a reference to any arbitrary memory location, a program typically only intends to use the pointer to access limited portions of memory, such as contiguous memory used to access an individual array. Programs may use offsets in order to access fields or sub-elements stored within structured data. The offset might be out-of-range if it comes from an untrusted source, is the result of an incorrect calculation, or occurs because of another error. If an attacker can control or influence the offset so that it points outside of the intended boundaries of the structure, then the attacker may be able to read or write to memory locations that are used elsewhere in the product. As a result, the attack might change the state of the product as accessed through program variables, cause a crash or instable behavior, and possibly lead to code execution.
Last updated: 21 August 2026 07:11 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 2 mapping(s) from 2 framework(s): CAPEC 1 (partial) · STIG windows 10 1 (partial)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls that address this weakness (0)AI-assisted
| 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-2023-33106 KEV UPD | 8.9 | 8.4 | 0.0085 | 2023-12-05 |
CVE-2023-24855 UPD | 7.3 | 9.8 | 0.0054 | 2023-10-03 |
CVE-2023-22388 UPD | 7.2 | 9.8 | 0.0035 | 2023-11-07 |
CVE-2023-43553 UPD | 7.2 | 9.8 | 0.0035 | 2024-03-04 |
CVE-2017-11076 UPD | 7.2 | 9.8 | 0.0034 | 2024-11-26 |
CVE-2016-2161 UPD | 7.1 | 7.5 | 0.2095 | 2017-07-27 |
CVE-2020-6112 UPD | 7.0 | 7.8 | 0.1709 | 2020-09-17 |
CVE-2020-27009 UPD | 6.9 | 8.1 | 0.0719 | 2021-04-22 |
CVE-2022-0729 UPD | 6.9 | 8.8 | 0.0162 | 2022-02-23 |
CVE-2023-46724 UPD | 6.8 | 8.6 | 0.0405 | 2023-11-01 |
CVE-2026-46244 UPD | 6.8 | 9.1 | 0.0032 | 2026-06-03 |
CVE-2026-21732 UPD | 6.6 | 9.6 | 0.0029 | 2026-03-20 |
CVE-2026-72642 | 6.5 | 8.8 | 0.0033 | 2026-08-13 |
CVE-2020-13573 UPD | 6.4 | 7.5 | 0.0342 | 2021-01-07 |
CVE-2021-3888 UPD | 6.4 | 8.1 | 0.0129 | 2021-10-19 |
CVE-2021-3889 UPD | 6.4 | 8.1 | 0.0129 | 2021-10-19 |
CVE-2023-43534 UPD | 6.4 | 8.6 | 0.0026 | 2024-02-06 |
CVE-2021-34595 UPD | 6.3 | 8.1 | 0.0088 | 2021-10-26 |
CVE-2022-32142 UPD | 6.3 | 8.1 | 0.0102 | 2022-06-24 |
CVE-2023-20187 UPD | 6.3 | 8.6 | 0.0065 | 2023-09-27 |
CVE-2022-0554 UPD | 6.2 | 7.8 | 0.0161 | 2022-02-10 |
CVE-2022-0685 UPD | 6.2 | 7.8 | 0.0172 | 2022-02-20 |
CVE-2024-42416 UPD | 6.2 | 8.8 | 0.0040 | 2024-09-05 |
CVE-2024-42386 | 6.2 | 8.2 | 0.0035 | 2024-11-18 |
CVE-2026-12290 UPD | 6.1 | 8.1 | 0.0040 | 2026-06-16 |