CVE-2026-74900: jahlives openssl_encrypt · Unchecked Error Condition
Affects jahlives openssl_encryptSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 1.4.0 as a priority.
Data as of 14 Nov 2026, 20:44 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.
What to do
Upgrade jahlives openssl_encrypt to 1.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jahlivesopenssl_encrypt | Affected
| Fixed in
|
AI-suggested
A fixed version 1.4.0 or later is available that addresses this vulnerability. Users should upgrade to version 1.4.0 or newer to remediate this issue. No other mitigation or workaround is indicated.
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.