A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference.

What CVEs are caused by CWE-466?

8 recorded CVEs are attributed to CWE-466, including CVE-2024-21849, CVE-2024-33602, CVE-2018-25234.

What are the consequences of CWE-466?

Exploiting CWE-466 can lead to: Read Memory, Modify Memory.

Is CWE-466 actively exploited?

8 recorded CVEs are caused by CWE-466; none are currently in CISA's KEV catalog of actively exploited flaws.

CWE-466: Return of Pointer Value Outside of Expected Range

Overview

CWE-466 (Return of Pointer Value Outside of Expected Range) is a base-level software weakness catalogued by MITRE in the Common Weakness Enumeration (CWE). It describes a recurring type of mistake that can lead to exploitable security vulnerabilities.

Real-world CVEs

8 recorded CVEs are caused by CWE-466 (Return of Pointer Value Outside of Expected Range). The highest-severity and most recent are shown first. 6 new CWE-466 CVEs have been recorded so far in 2026.

CVE-2024-21849
High · CVSS 7.5 · EPSS 42th
2024-02-14
CVE-2024-33602
nscd: netgroup cache assumes NSS callback uses in-buffer strings
High · CVSS 7.4 · EPSS 33th
2024-05-06
CVE-2018-25234
SmartFTP Client 9.0.2615.0 Denial of Service via Host Field
Medium · CVSS 6.9 · EPSS 11th
2026-03-30
CVE-2018-25227
Valentina Studio 9.0.4 Denial of Service via Host Parameter
Medium · CVSS 6.9 · EPSS 11th
2026-03-30
CVE-2019-25599
Backup Key Recovery 2.2.4 Denial of Service via Name Field
Medium · CVSS 6.9 · EPSS 2th
2026-03-22
CVE-2019-25586
Deluge 1.3.15 Denial of Service via URL Field
Medium · CVSS 6.9 · EPSS 7th
2026-03-22
CVE-2019-25548
BlueStacks 4.80.0.1060 Denial of Service via Search Field
Medium · CVSS 6.9 · EPSS 6th
2026-03-21
CVE-2026-57025
Junos OS and Junos OS Evolved: EX Series, QFX Series, MX Series: A specific 'show l2-learning/ethernet-switching' command causes l2ald crash
Medium · CVSS 6.8 · EPSS 4th
2026-07-09

Common consequences

What can happen when CWE-466 is exploited.

Read Memory, Modify Memory

Affects: Confidentiality, Integrity

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Implementation

Applies to

Languages

Memory-Unsafe

C

C++

How to detect it

Automated Static Analysis

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

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].

Effectiveness: Moderate

How this weakness relates to others in the CWE hierarchy.

Parent

Terminology & mappings

Mapped taxonomies

7 Pernicious Kingdoms: Illegal Pointer Value
Software Fault Patterns: Glitch in computation (SFP1)

Frequently asked questions

Common questions about CWE-466.

What is CWE-466?: A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference.
What CVEs are caused by CWE-466?: 8 recorded CVEs are attributed to CWE-466, including CVE-2024-21849, CVE-2024-33602, CVE-2018-25234.
How is CWE-466 detected?: Automated Static Analysis: 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.)
What are the consequences of CWE-466?: Exploiting CWE-466 can lead to: Read Memory, Modify Memory.
Is CWE-466 actively exploited?: 8 recorded CVEs are caused by CWE-466; none are currently in CISA's KEV catalog of actively exploited flaws.

References

Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.