CWE · MITRE source
CWE-338Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
When a non-cryptographic PRNG is used in a cryptographic context, it can expose the cryptography to certain types of attacks. Often a pseudo-random number generator (PRNG) is not designed for cryptography. Sometimes a mediocre source of randomness is sufficient or preferable for algorithms that use random numbers. Weak generators generally take less processing power and/or do not use the precious, finite, entropy sources on a system. While such PRNGs might have very useful features, these same features could be used to break the cryptography.
Last updated: 22 August 2026 14: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: mostly · 3 mapping(s) from 3 framework(s): STIG oracle linux 8 1 (mostly) · STIG ubuntu 22 04 1 (mostly) · STIG rhel 8 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.
—
- 3 hardening rules · 3 OS baselines
V7.2.3V11.5.1
NIST 800-53 r5 controls that address this weakness (2)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AT-5 | Contacts with Security Groups and Associations | AT | Security associations share details on cryptographically weak PRNGs, helping avoid their implementation in security-critical functions. |
SC-12 | Cryptographic Key Establishment and Management | SC | Cryptographic key management standards require cryptographically strong PRNGs for key material, blocking use of weak generators. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2009-2367 UPD | 8.6 | 9.8 | 0.2319 | 2009-07-08 |
CVE-2008-0166 UPD | 8.4 | 7.5 | 0.7072 | 2008-05-13 |
CVE-2019-16303 UPD | 7.8 | 9.8 | 0.0367 | 2019-09-14 |
CVE-2017-18021 UPD | 7.7 | 9.8 | 0.0236 | 2018-01-05 |
CVE-2015-9435 UPD | 7.7 | 9.8 | 0.0206 | 2019-09-26 |
CVE-2020-28642 UPD | 7.7 | 9.8 | 0.0255 | 2020-11-16 |
CVE-2021-3538 UPD | 7.7 | 9.8 | 0.0231 | 2021-06-02 |
CVE-2024-29868 UPD | 7.6 | 9.1 | 0.0600 | 2024-06-24 |
CVE-2019-14480 UPD | 7.5 | 9.8 | 0.0112 | 2020-12-16 |
CVE-2011-4574 UPD | 7.5 | 9.8 | 0.0109 | 2021-10-27 |
CVE-2023-36993 UPD | 7.5 | 9.8 | 0.0096 | 2023-07-07 |
CVE-2024-40762 UPD | 7.5 | 9.8 | 0.0104 | 2025-01-09 |
CVE-2022-44796 UPD | 7.4 | 9.8 | 0.0069 | 2022-11-07 |
CVE-2023-2884 UPD | 7.4 | 9.8 | 0.0069 | 2023-05-25 |
CVE-2025-3495 UPD | 7.4 | 9.8 | 0.0067 | 2025-04-16 |
CVE-2025-59390 UPD | 7.4 | 9.8 | 0.0061 | 2025-11-26 |
CVE-2026-61500 | 7.4 | 9.8 | 0.0075 | 2026-07-13 |
CVE-2025-7394 UPD | 7.3 | 9.8 | 0.0039 | 2025-07-18 |
CVE-2025-66565 | 7.3 | 9.8 | 0.0046 | 2025-12-09 |
CVE-2025-68932 | 7.3 | 9.8 | 0.0053 | 2025-12-27 |
CVE-2026-2439 UPD | 7.3 | 9.8 | 0.0040 | 2026-02-16 |
CVE-2025-40926 | 7.3 | 9.8 | 0.0043 | 2026-03-05 |
CVE-2025-15604 | 7.3 | 9.8 | 0.0052 | 2026-03-28 |
CVE-2026-3256 UPD | 7.3 | 9.8 | 0.0053 | 2026-03-28 |
CVE-2026-56141 | 7.3 | 9.8 | 0.0052 | 2026-06-19 |