CVE-2026-74876
Jahlives OpenSSL Encrypt vulnerability
- Published17 Aug 2026
Description
openssl_encrypt versions before 1.4.0 contain a vulnerability in PublicKeyBundle.from_dict() that creates key bundles from untrusted data without verifying signatures. Attackers can call from_dict() followed by to_identity() without signature verification to encrypt data using attacker-controlled public keys, leaking secrets.
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-74876 being actively exploited?
CVE-2026-74876 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.35%.
How severe is CVE-2026-74876?
CVE-2026-74876 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.35% probability of exploitation.
Which products are affected by CVE-2026-74876?
Affected products include Jahlives OpenSSL Encrypt.
How do I fix CVE-2026-74876?
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-74876 against the real software inventory on every managed device, as each hourly inventory arrives. 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.