CWE · MITRE source
CWE-325Missing Cryptographic Step
The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.
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: mostly · 10 mapping(s) from 9 framework(s): STIG oracle linux 8 2 (mostly) · STIG rhel 8 1 (mostly) · STIG ubuntu 22 04 1 (mostly) · STIG ubuntu 24 04 1 (mostly) · STIG oracle linux 9 1 (mostly) · OWASP-Web 1 (mostly) · CAPEC 1 (partial) · STIG rhel 7 1 (partial) · ATT&CK 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A04:2025 Cryptographic Failures.
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).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2020-15086 | 7.0 | 9.8 | 0.0272 | 2020-07-29 |
CVE-2022-24116 | 7.0 | 9.8 | 0.0029 | 2022-12-26 |
CVE-2020-15098 | 5.5 | 8.8 | 0.0223 | 2020-07-29 |
CVE-2021-33560 | 5.5 | 7.5 | 0.0234 | 2021-06-08 |
CVE-2021-22946 | 5.5 | 7.5 | 0.0422 | 2021-09-29 |
CVE-2022-20742 | 5.5 | 7.4 | 0.0043 | 2022-05-03 |
CVE-2023-46129 | 5.5 | 7.5 | 0.0037 | 2023-10-31 |
CVE-2025-60704 | 5.5 | 7.5 | 0.0048 | 2025-11-11 |
CVE-2026-22863 | 5.5 | 7.5 | 0.0019 | 2026-01-15 |
CVE-2025-47383 | 5.5 | 7.2 | 0.0013 | 2026-03-02 |
CVE-2026-28498 UPD | 5.5 | 7.5 | 0.0023 | 2026-03-16 |
CVE-2026-4258 UPD | 5.5 | 7.5 | 0.0025 | 2026-03-17 |
CVE-2026-4601 UPD | 5.5 | 8.7 | 0.0030 | 2026-03-23 |
CVE-2026-40542 UPD | 5.5 | 7.3 | 0.0046 | 2026-04-22 |
CVE-2026-41395 | 5.5 | 7.5 | 0.0015 | 2026-04-28 |
CVE-2026-42246 UPD | 5.5 | 7.4 | 0.0032 | 2026-05-09 |
CVE-2026-45445 UPD | 5.5 | 7.5 | 0.0032 | 2026-06-09 |
CVE-2026-49440 | 5.5 | 7.4 | 0.0015 | 2026-06-23 |
CVE-2017-2600 | 3.5 | 4.3 | 0.0110 | 2018-05-15 |
CVE-2017-2603 | 3.5 | 2.6 | 0.0107 | 2018-05-15 |
CVE-2017-2598 | 3.5 | 4.3 | 0.0110 | 2018-05-23 |
CVE-2016-9574 | 3.5 | 5.9 | 0.0140 | 2018-07-19 |
CVE-2018-5383 | 3.5 | 6.8 | 0.0080 | 2018-08-07 |
CVE-2019-3738 | 3.5 | 6.5 | 0.0168 | 2019-09-18 |
CVE-2020-10702 | 3.5 | 5.5 | 0.0033 | 2020-06-04 |