CVE-2026-74887
openssl_encrypt (Python) imported non-cryptographic random risking predictable cryptographic outputs.
Is CVE-2026-74887 being exploited?
Not confirmed. CVE-2026-74887 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.18% probability of exploitation in the next 30 days.
How severe is CVE-2026-74887?
CVE-2026-74887 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-74887?
Yes. A fix has been recorded for CVE-2026-74887. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74887 affect?
CVE-2026-74887 affects openssl_encrypt <1.4.0, Python applications using openssl_encrypt, openssl_encrypt/modules/pqc.py. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74887?
Upgrade to openssl_encrypt 1.4.0 and audit for random.* usage in crypto code.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Imported Mersenne Twister can lead to predictable RNG; attackers recovering MT state (~624 outputs) can predict keys/nonces enabling key recovery or forgery.
Patch when possible
- affected< 1.4.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.