CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
191 CVEs have CWE-338 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 70.721%.
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.
Child of CWE-330: Use of Insufficiently Random Values
Mitigations
- Implementation: Use functions or hardware which use a hardware-based random number generation for all crypto. This is the recommended solution. Use CyptGenRandom on Windows, or hw_rand() on Linux.
Observed examples
- CVE-2021-3692: PHP framework uses mt_rand() function (Marsenne Twister) when generating tokens
- CVE-2009-3278: Crypto product uses rand() library function to generate a recovery key, making it easier to conduct brute force attacks.
- CVE-2009-3238: Random number generator can repeatedly generate the same value.
- CVE-2009-2367: Web application generates predictable session IDs, allowing session hijacking.
- CVE-2008-0166: SSL library uses a weak random number generator that only generates 65,536 unique keys.
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2026-18564 | 2026-11-16 | MEDIUM | 6.9 | not scored | LibreOffice can export documents to PDF protected by a password. With the PDF 2.0 option the file is encrypted with 256-bit AES, using a file encryption key… |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-338'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-338'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).