CVE-2026-74875
Jahlives OpenSSL Encrypt vulnerability
- Published17 Aug 2026
Description
openssl_encrypt versions before 1.4.0 silently skip JSON schema validation when the jsonschema library is not installed, allowing malformed metadata to be accepted. Attackers can remove the jsonschema package or supply unknown metadata format versions to bypass all schema checks and process malicious data.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-74875 being actively exploited?
CVE-2026-74875 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.27%.
How severe is CVE-2026-74875?
CVE-2026-74875 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.27% probability of exploitation.
Which products are affected by CVE-2026-74875?
Affected products include Jahlives OpenSSL Encrypt.
How do I fix CVE-2026-74875?
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-74875 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.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.