CWE · MITRE source
CWE-667Improper Locking
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.
Last updated: 20 August 2026 13:14 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 · 3 mapping(s) from 1 framework(s): CAPEC 3 (partial)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
PR.PS-06
—
—
—
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-2025-43510 KEV UPD | 8.5 | 7.8 | 0.0036 | 2025-12-12 |
CVE-2019-10072 UPD | 8.4 | 7.5 | 0.7299 | 2019-06-21 |
CVE-2021-1782 KEV UPD | 7.9 | 7.0 | 0.0222 | 2021-04-02 |
CVE-2020-12658 UPD | 7.6 | 9.8 | 0.0168 | 2020-12-31 |
CVE-2019-5886 UPD | 7.5 | 9.8 | 0.0099 | 2019-01-10 |
CVE-2021-47587 UPD | 7.3 | 9.8 | 0.0055 | 2024-06-19 |
CVE-2024-58087 UPD | 7.3 | 9.8 | 0.0049 | 2025-03-12 |
CVE-2026-53049 UPD | 7.3 | 9.8 | 0.0039 | 2026-06-24 |
CVE-2025-22077 UPD | 7.2 | 9.8 | 0.0035 | 2025-04-16 |
CVE-2026-54906 | 7.1 | 9.8 | 0.0016 | 2026-06-24 |
CVE-2002-1850 UPD | 7.0 | 7.5 | 0.1741 | 2002-12-31 |
CVE-2009-2699 UPD | 6.9 | 7.5 | 0.1417 | 2009-10-13 |
CVE-2020-24606 UPD | 6.9 | 8.6 | 0.0516 | 2020-08-24 |
CVE-2004-0174 UPD | 6.8 | 7.5 | 0.1155 | 2004-05-04 |
CVE-2009-4272 UPD | 6.8 | 7.5 | 0.1105 | 2010-01-27 |
CVE-2018-0228 UPD | 6.8 | 8.6 | 0.0361 | 2018-04-19 |
CVE-2020-15674 UPD | 6.7 | 8.8 | 0.0081 | 2020-10-01 |
CVE-2020-0303 UPD | 6.6 | 8.8 | 0.0056 | 2020-09-17 |
CVE-2023-32258 UPD | 6.6 | 8.1 | 0.0251 | 2023-07-24 |
CVE-2023-32257 UPD | 6.5 | 8.1 | 0.0239 | 2023-07-24 |
CVE-2026-43215 UPD | 6.5 | 8.8 | 0.0030 | 2026-05-06 |
CVE-2006-2275 UPD | 6.4 | 7.5 | 0.0360 | 2006-05-09 |
CVE-2006-5158 UPD | 6.4 | 7.5 | 0.0347 | 2006-10-05 |
CVE-2021-1622 UPD | 6.4 | 8.6 | 0.0098 | 2021-09-23 |
CVE-2022-48785 UPD | 6.4 | 8.8 | 0.0025 | 2024-07-16 |