What CVEs are caused by CWE-414?

3 recorded CVEs are attributed to CWE-414, including CVE-2025-54625, CVE-2025-54510, CVE-2026-54906.

What are the consequences of CWE-414?

Exploiting CWE-414 can lead to: Modify Application Data, DoS: Instability, DoS: Crash, Exit, or Restart.

Is CWE-414 actively exploited?

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

RadicalNotion.AI

Log in Start free

Log in

Log in Start free

Base weakness

Draft

CWE-414: Missing Lock Check

A product does not check to see if a lock is present before performing sensitive operations on a resource.

Last updated May 1, 2026

3

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-414 (Missing Lock Check) 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

3 recorded CVEs are caused by CWE-414 (Missing Lock Check). The highest-severity and most recent are shown first. 2 new CWE-414 CVEs have been recorded so far in 2026 (1 in 2025).

Common consequences

What can happen when CWE-414 is exploited.

Modify Application Data, DoS: Instability, DoS: Crash, Exit, or Restart

Affects: Integrity, Availability

How it happens

When it is introduced

Typically introduced during these phases of the software lifecycle.

Architecture and Design

Implementation

How to prevent it

Practical mitigations for CWE-414, grouped by where in the lifecycle they apply.

Architecture and Design

Implementation

Implement a reliable lock mechanism.

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

Illustrative examples

Real CVEs that MITRE cites as examples of this weakness.

CVE-2004-1056 — Product does not properly check if a lock is present, allowing other attackers to access functionality.

Terminology & mappings

Mapped taxonomies

PLOVER: Missing Lock Check
Software Fault Patterns: Missing Lock (SFP19)

Frequently asked questions

Common questions about CWE-414.

What is CWE-414?: A product does not check to see if a lock is present before performing sensitive operations on a resource.
What CVEs are caused by CWE-414?: 3 recorded CVEs are attributed to CWE-414, including CVE-2025-54625, CVE-2025-54510, CVE-2026-54906.
How do you prevent CWE-414?: Implement a reliable lock mechanism.
How is CWE-414 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-414?: Exploiting CWE-414 can lead to: Modify Application Data, DoS: Instability, DoS: Crash, Exit, or Restart.
Is CWE-414 actively exploited?: 3 recorded CVEs are caused by CWE-414; 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-414

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

Start free See pricing