Security Resilience

CWE · MITRE source

CWE-820Missing Synchronization

Abstraction: Base · CVEs in our corpus: 16

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

If access to a shared resource is not 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: 15 October 2026 14:21 UTC

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.PS-06
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)

—

NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted

These are model PROPOSALS, not graded mappings. They come from controls_to_cwe_proposals, which carries no grade field at all; across the CWE pages 1,540 of 1,722 such associations (89%) have never been graded by anything. The heading said “address” until 2026-09-29, which asserted a relationship the data does not carry. Graded cross-walks are on the framework map, not here.

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-47154 6.49.00.00682025-05-01
CVE-2023-2801 6.07.50.00752023-06-06
CVE-2024-49114 6.07.80.00752024-12-12
CVE-2026-53277 5.98.80.00112026-06-25
CVE-2026-50013 5.97.50.00472026-09-11
CVE-2025-1445 5.87.50.00332025-03-25
CVE-2026-53153 5.57.80.00102026-06-25
CVE-2022-50238 5.47.40.00242025-09-08
CVE-2025-47999 5.16.80.00482025-07-08
CVE-2025-49751 5.16.80.00492025-08-12
CVE-2026-22163 5.17.80.00082026-03-20
CVE-2026-44318 5.06.50.00332026-05-27
CVE-2023-45084 4.97.00.00222023-12-05
CVE-2024-30387 4.96.50.00212024-04-12
CVE-2026-70637 4.65.90.00372026-08-06
CVE-2026-570294.15.30.00192026-07-09