CWE-414: Missing Lock Check
4 CVEs have CWE-414 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 0.160%.
A product does not check to see if a lock is present before performing sensitive operations on a resource.
Child of CWE-667: Improper Locking
Mitigations
- Architecture and Design Implementation: Implement a reliable lock mechanism.
Observed examples
- CVE-2026-54906: Ruby-based concurrency package does not verify that its calling thread had aquired a write lock.
- CVE-2023-5447: Chain: missing lock check (CWE-414) leads to Use-After-Free (CWE-416)
- CVE-2004-1056: Product does not properly check if a lock is present, allowing other attackers to access functionality.
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-414'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-414'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).