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: 15 October 2026 14:21 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 · 7 mapping(s) from 6 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) · STIG rhel 7 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A04:2025 Cryptographic Failures.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
- 14 hardening rules · 6 OS baselines
—
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-2020-15086 UPD | 7.8 | 9.8 | 0.0356 | 2020-07-29 |
CVE-2022-24116 UPD | 7.2 | 9.8 | 0.0030 | 2022-12-26 |
CVE-2020-15098 UPD | 7.0 | 8.8 | 0.0223 | 2020-07-29 |
CVE-2026-17666 | 6.6 | 9.1 | 0.0017 | 2026-07-30 |
CVE-2021-22946 UPD | 6.5 | 7.5 | 0.0454 | 2021-09-29 |
CVE-2021-33560 UPD | 6.3 | 7.5 | 0.0237 | 2021-06-08 |
CVE-2026-4601 UPD | 6.2 | 8.7 | 0.0047 | 2026-03-23 |
CVE-2026-45445 UPD | 6.0 | 7.5 | 0.0070 | 2026-06-09 |
CVE-2026-101294 | 6.0 | 8.7 | 0.0021 | 2026-10-13 |
CVE-2026-100798 | 5.9 | 8.1 | 0.0020 | 2026-09-29 |
CVE-2023-46129 UPD | 5.8 | 7.5 | 0.0037 | 2023-10-31 |
CVE-2025-60704 | 5.8 | 7.5 | 0.0057 | 2025-11-11 |
CVE-2026-4258 UPD | 5.8 | 7.5 | 0.0036 | 2026-03-17 |
CVE-2026-40542 UPD | 5.8 | 7.3 | 0.0070 | 2026-04-22 |
CVE-2022-20742 UPD | 5.7 | 7.4 | 0.0046 | 2022-05-03 |
CVE-2026-22863 | 5.7 | 7.5 | 0.0020 | 2026-01-15 |
CVE-2026-28498 UPD | 5.7 | 7.5 | 0.0027 | 2026-03-16 |
CVE-2026-41395 | 5.7 | 7.5 | 0.0025 | 2026-04-28 |
CVE-2026-42246 UPD | 5.6 | 7.4 | 0.0031 | 2026-05-09 |
CVE-2026-49440 | 5.5 | 7.4 | 0.0024 | 2026-06-23 |
CVE-2026-81235 | 5.5 | 8.0 | 0.0024 | 2026-09-15 |
CVE-2018-5383 UPD | 5.4 | 6.8 | 0.0081 | 2018-08-07 |
CVE-2019-3738 UPD | 5.4 | 6.5 | 0.0168 | 2019-09-18 |
CVE-2020-26244 UPD | 5.4 | 6.8 | 0.0083 | 2020-12-02 |
CVE-2026-55144 | 5.3 | 7.1 | 0.0022 | 2026-07-14 |