Log inLog in

Base weakness

Incomplete

CWE-475: Undefined Behavior for Input to API

The behavior of this function is undefined unless its control parameter is set to a specific value.

Last updated May 1, 2026

11

Recorded CVEs

With this primary weakness

0

KEVs

In the CISA KEV catalog

Not rated

Likelihood of exploit

Per MITRE

Base

Abstraction

MITRE classification

Overview

CWE-475 (Undefined Behavior for Input to API) 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

11 recorded CVEs are caused by CWE-475 (Undefined Behavior for Input to API). The highest-severity and most recent are shown first. 1 new CWE-475 CVE has been recorded so far in 2026 (3 in 2025).

CVE-2024-20380

High · CVSS 7.5 · EPSS 66th

2024-04-18

CVE-2020-7925

High · CVSS 7.5 · EPSS 82th

2020-11-23

CVE-2023-2253

Medium · CVSS 6.5 · EPSS 35th

2023-06-06

CVE-2024-3099

Medium · CVSS 5.4 · EPSS 20th

2024-06-06

CVE-2023-52533

Medium · CVSS 5.3 · EPSS 76th

2024-04-08

CVE-2025-47866

Medium · CVSS 4.3 · EPSS 55th

2025-06-17

CVE-2023-4874

Medium · CVSS 4.3 · EPSS 26th

2023-09-09

CVE-2023-4875

Low · CVSS 2.2 · EPSS 9th

2023-09-09

Common consequences

What can happen when CWE-475 is exploited.

Quality Degradation, Varies by Context

Affects: Other

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Architecture and Design

Implementation

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

Effectiveness: High

Terminology & mappings

Mapped taxonomies

7 Pernicious Kingdoms: Undefined Behavior
Software Fault Patterns: Glitch in computation (SFP1)

Frequently asked questions

Common questions about CWE-475.

What is CWE-475?

The behavior of this function is undefined unless its control parameter is set to a specific value.

What CVEs are caused by CWE-475?

11 recorded CVEs are attributed to CWE-475, including CVE-2026-42009, CVE-2025-47865, CVE-2024-10569.

How is CWE-475 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-475?

Exploiting CWE-475 can lead to: Quality Degradation, Varies by Context.

Is CWE-475 actively exploited?

11 recorded CVEs are caused by CWE-475; 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.

Stay ahead of CWE-475

Get alerted the moment a new CWE-475 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.

Start free See pricing