CVE-2026-74875: jahlives openssl_encrypt · Insufficient Verification of Data Authenticity
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 15 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% 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 15 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
A fix is available in jahlives openssl_encrypt version 1.4.0 and later. Users should upgrade to version 1.4.0 or newer to ensure JSON schema validation is properly enforced regardless of the presence of the jsonschema library. Until upgrading, ensure the jsonschema package is installed and not removed to maintain validation checks.
Description
CVE-2026-74875 is a critical vulnerability in the jahlives openssl_encrypt library versions before 1.4.0. When the jsonschema library is not installed, the software silently skips JSON schema validation, allowing malformed metadata to be accepted. Attackers can exploit this by removing the jsonschema package or supplying unknown metadata format versions to bypass schema checks and process malicious data.