CVE-2026-81702
Jahlives OpenSSL Encrypt vulnerability
- Published27 Aug 2026
Description
openssl_encrypt before 1.4.9 fails to re-derive and validate fingerprints when loading identities from identity.json, allowing attackers to substitute public keys in identity stores. Attackers can replace legitimate public keys with their own while maintaining the claimed fingerprint, enabling silent key substitution where encryption uses attacker keys and signature verification appears valid.
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-81702 being actively exploited?
CVE-2026-81702 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.19%.
How severe is CVE-2026-81702?
CVE-2026-81702 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.19% probability of exploitation.
Which products are affected by CVE-2026-81702?
Affected products include Jahlives OpenSSL Encrypt.
How do I fix CVE-2026-81702?
Upgrade affected software to a fixed version, for example Jahlives OpenSSL Encrypt 1.4.9 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-81702 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.