CVE-2026-74900

Jahlives OpenSSL Encrypt vulnerability

9.8 CRITICALEPSS 0.56%

Published17 Aug 2026

Description

openssl_encrypt versions before 1.4.0 contain a critical vulnerability in pqc.py where KEM decapsulation failures silently fall back to simulation mode, generating a deterministic shared secret from only 16 bytes of the private key and publicly available encapsulated key data. Attackers who obtain 16 bytes of the private key can compute the shared secret and decrypt all ciphertext, as the fallback triggers on any KEM failure without raising an error.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Jahlives OpenSSL Encrypt< 1.4.0

Remediation

Fixed in

Jahlives OpenSSL Encrypt≥ 1.4.0

Patch & vendor advisories

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-p3gq-pcg9-qvfv

References

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-p3gq-pcg9-qvfvMitigationVendor Advisory
https://www.vulncheck.com/advisories/openssl-encrypt-before-weak-shared-secret-via-pqc-simulation-modeThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-74900 being actively exploited?

CVE-2026-74900 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.56%.

How severe is CVE-2026-74900?

CVE-2026-74900 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.56% probability of exploitation.

Which products are affected by CVE-2026-74900?

Affected products include Jahlives OpenSSL Encrypt.

How do I fix CVE-2026-74900?

Upgrade affected software to a fixed version, for example Jahlives OpenSSL Encrypt 1.4.0 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-74900 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.