CVE-2026-74901: jahlives openssl_encrypt · Improper Verification of Cryptographic Signature
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.4% chance of exploitation in 30 days – higher than 35% 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 openssl_encrypt and jahlives/openssl_encrypt to 1.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| jahlivesopenssl_encrypt | Affected
| Fixed in
|
GitHubjahlives/openssl_encryptpkg:github/jahlives/openssl_encryptOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Avoid using affected versions (>=0 <1.4.0) in sensitive environments until a fix is available.
Description
openssl_encrypt versions before 1.4.0 contain an authentication bypass vulnerability in pqc.py where AES-GCM decryption failures trigger fallback to unauthenticated AES-CTR mode. Attackers can modify ciphertext in transit to bypass integrity verification and perform bit-flipping attacks without detection.