CVE-2026-74887: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in jahlives openssl_encrypt
openssl_encrypt before 1.4.0 imports Python's non-cryptographic 'random' module (Mersenne Twister PRNG) at line 15 of openssl_encrypt/modules/pqc.py. No direct calls to random.* were present in the code, so no cryptographic operation is currently affected; however, the import creates a hazard that future code could inadvertently use random.randint() instead of a cryptographically secure alternative (secrets/os.urandom), producing predictable values since the Mersenne Twister state can be recovered from approximately 624 outputs. Fixed by removing the import in 1.4.0.
AI Analysis
Technical Summary
The vulnerability in jahlives openssl_encrypt prior to version 1.4.0 stems from importing Python's standard random module, which uses the Mersenne Twister PRNG, a non-cryptographically secure generator. Although the current code does not call random functions directly, the presence of this import creates a hazard where future code might mistakenly use random.randint() instead of secure alternatives like secrets or os.urandom. Since the Mersenne Twister's internal state can be reconstructed from about 624 outputs, this could lead to predictable random values, undermining cryptographic security. The issue was addressed by removing the import in version 1.4.0.
Potential Impact
If exploited, this vulnerability could allow attackers to predict random values generated by the module if future code uses the insecure random module, potentially compromising cryptographic operations. However, no direct exploitation is currently known, and the existing code does not use the insecure random functions. The CVSS 4.0 score of 9.3 indicates a critical severity due to the potential for high impact if the hazard is realized.
Mitigation Recommendations
Upgrade to jahlives openssl_encrypt version 1.4.0 or later, where the insecure import of the random module has been removed. This eliminates the risk of inadvertently using a cryptographically weak PRNG. Since no official patch link or advisory is provided, verify the upgrade availability from the vendor or project repository. Patch status is not yet confirmed beyond the stated fix in version 1.4.0; check vendor sources for current remediation guidance.
CVE-2026-74887: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in jahlives openssl_encrypt
Description
openssl_encrypt before 1.4.0 imports Python's non-cryptographic 'random' module (Mersenne Twister PRNG) at line 15 of openssl_encrypt/modules/pqc.py. No direct calls to random.* were present in the code, so no cryptographic operation is currently affected; however, the import creates a hazard that future code could inadvertently use random.randint() instead of a cryptographically secure alternative (secrets/os.urandom), producing predictable values since the Mersenne Twister state can be recovered from approximately 624 outputs. Fixed by removing the import in 1.4.0.
CVSS v4.0
Score 9.3critical
Affected software
pkg:github/jahlives/openssl_encryptRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in jahlives openssl_encrypt prior to version 1.4.0 stems from importing Python's standard random module, which uses the Mersenne Twister PRNG, a non-cryptographically secure generator. Although the current code does not call random functions directly, the presence of this import creates a hazard where future code might mistakenly use random.randint() instead of secure alternatives like secrets or os.urandom. Since the Mersenne Twister's internal state can be reconstructed from about 624 outputs, this could lead to predictable random values, undermining cryptographic security. The issue was addressed by removing the import in version 1.4.0.
Potential Impact
If exploited, this vulnerability could allow attackers to predict random values generated by the module if future code uses the insecure random module, potentially compromising cryptographic operations. However, no direct exploitation is currently known, and the existing code does not use the insecure random functions. The CVSS 4.0 score of 9.3 indicates a critical severity due to the potential for high impact if the hazard is realized.
Mitigation Recommendations
Upgrade to jahlives openssl_encrypt version 1.4.0 or later, where the insecure import of the random module has been removed. This eliminates the risk of inadvertently using a cryptographically weak PRNG. Since no official patch link or advisory is provided, verify the upgrade availability from the vendor or project repository. Patch status is not yet confirmed beyond the stated fix in version 1.4.0; check vendor sources for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-17T10:42:40.455Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a82f004bf8831d539c48362
Added to database: 08/17/2026, 11:27:00 UTC
Last enriched: 08/17/2026, 11:42:35 UTC
Last updated: 08/17/2026, 13:16:32 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.