CVE-2026-74887

Unspecified impact via stray PRNG import

Published Aug 17, 2026 · Updated Aug 18, 2026

Insecure randomness in jahlives openssl_encrypt before 1.4.0 allows attackers to cause unspecified impact via a stray PRNG import. At line 15 of openssl_encrypt/modules/pqc.py, the PQC module imports Python's random module, placing a Mersenne Twister source beside cryptographic code even though the published records identify no current random.* call. Reaching a real exploit would require later code changes or an undisclosed execution path to draw security-sensitive values from that module; the published records describe no current confidentiality, integrity, or availability effect.

CVSS severity9.3
Critical
EPSS probability0.18%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Insecure randomness in jahlives openssl_encrypt before 1.4.0 allows attackers to cause unspecified impact via a stray PRNG import. At line 15 of openssl_encrypt/modules/pqc.py, the PQC module imports Python's random module, placing a Mersenne Twister source beside cryptographic code even though the published records identify no current random.* call. Reaching a real exploit would require later code changes or an undisclosed execution path to draw security-sensitive values from that module; the published records describe no current confidentiality, integrity, or availability effect.

The record

CVE
CVE-2026-74887
Published
Aug 17, 2026
Updated
Aug 18, 2026
Vendor
jahlives
Product
OpenSSL Encrypt
Classifications
CWE-338
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Aug 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 18, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <1.4.0

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

jahlives · OpenSSL Encryptversion=0 <1.4.0

Published CVSS scores

0.0VulnCheckCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:N
9.3VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-338Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo