CVE-2026-81700
Jahlives OpenSSL Encrypt vulnerability
- Published27 Aug 2026
Description
openssl_encrypt versions before 1.4.9 contain a signature verification vulnerability in gpg_runner.verify_detached that accepts revoked and expired keys by only checking VALIDSIG status without inspecting REVKEYSIG, EXPKEYSIG, or gpg exit codes. Attackers holding compromised-then-revoked signing keys or expired project keys can bypass signature verification to execute malicious plugins in the host process.
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-81700 being actively exploited?
CVE-2026-81700 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.35%.
How severe is CVE-2026-81700?
CVE-2026-81700 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-81700?
Affected products include Jahlives OpenSSL Encrypt.
How do I fix CVE-2026-81700?
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-81700 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.