Cyber Resilience

CWE · MITRE source

CWE-821Incorrect Synchronization

Abstraction: Base · CVEs in our corpus: 13

The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.

If access to a shared resource is not correctly synchronized, then the resource may not be in a state that is expected by the product. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource.

Last updated: 04 July 2026 00:28 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 · 2 mapping(s) from 1 framework(s): ATT&CK 2 (partial)

See the full cumulative-coverage rollup →

NIST 800-53 r5 controls that address this weakness (0)AI

Control Title Family Why it addresses this CWE
No NIST controls proposed yet.

MITRE ATT&CK techniques this weakness enables

Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.

Direction: ← other covers this; → this covers other (F/M/P = full / mostly / partial).

T1068 Exploitation for Privilege Escalation←P →PT1548 Abuse Elevation Control Mechanism←P →P

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2024-17397.09.10.00562024-04-16
CVE-2026-43198 UPD7.09.80.00292026-05-06
CVE-2022-19315.58.10.01952022-05-31
CVE-2024-19025.57.50.00392024-04-10
CVE-2023-50883.56.40.00232023-11-03
CVE-2024-57553.55.30.00342024-06-27
CVE-2024-42783.55.50.00232024-09-26
CVE-2024-66573.56.50.00192024-10-11
CVE-2024-581313.54.00.00232025-04-06
CVE-2024-581323.54.00.00242025-04-06
CVE-2024-581333.54.00.00242025-04-06
CVE-2026-219193.56.50.00232026-04-09
CVE-2026-561323.56.90.00092026-06-19