CVE-2026-81701
Jahlives OpenSSL Encrypt vulnerability
- Published27 Aug 2026
Description
openssl_encrypt versions before 1.4.9 use a denylist to identify trusted built-in plugins, allowing unsigned plugins in top-level plugins/ directories and unknown subdirectories to bypass signature verification. Attackers can place malicious unsigned plugins following documented installation paths to achieve arbitrary code execution in the CLI process with access to passwords and cryptographic keys.
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-81701 being actively exploited?
CVE-2026-81701 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.43%.
How severe is CVE-2026-81701?
CVE-2026-81701 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.43% probability of exploitation.
Which products are affected by CVE-2026-81701?
Affected products include Jahlives OpenSSL Encrypt.
How do I fix CVE-2026-81701?
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-81701 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.