CVE-2026-81700

openssl_encrypt before 1.4.9 GPG Signature Verification Bypass

Published Aug 27, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability lies in a GPG signature verification routine in openssl_encrypt that only checks for a valid signature status without checking for revoked or expired keys or GPG exit codes, allowing attackers with previously revoked or expired signing keys to bypass the check and inject malicious plugins into the host process. This can lead to the execution of arbitrary code within the application context.

Affected Systems

The flaw affects the openssl_encrypt package provided by jahlives. Versions prior to 1.4.9 are vulnerable; users should verify their installed version and upgrade if it falls below 1.4.9.

Risk and Exploitability

The CVSS score of 9.3 indicates critical severity and the lack of KEV listing does not diminish the risk. Since the exploit requires only knowledge of a compromised but now revoked or expired key, the attack vector is local to the application’s plugin infrastructure, meaning attackers can leverage user‑provided keys to execute malicious code on the target host. The EPSS score is not available, so the current exploitation probability is unknown, but the high CVSS score suggests a potentially significant threat.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade openssl_encrypt to version 1.4.9 or later, which contains the signature verification fix.
  • If an immediate upgrade is not possible, configure the application to reject any signatures that fail VALID SIG, EXPKEYSIG, or REVKEYSIG checks, or use a GPG verification tool that inspects exit codes and rejects revoked or expired keys.
  • Disable or limit plugin execution from untrusted sources until the vulnerability is resolved, ensuring that only trusted plugins are loaded.

Generated by OpenCVE AI on August 27, 2026 at 17:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:*:*:*
Type Values Removed Values Added
CPEs cpe:2.3:a:jahlives:openssl_encrypt:*:*:*:*:*:python:*:*
Type Values Removed Values Added
First Time appeared Jahlives
Jahlives openssl Encrypt
Vendors & Products Jahlives
Jahlives openssl Encrypt
Type Values Removed Values Added
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.
Title openssl_encrypt before 1.4.9 GPG Signature Verification Bypass
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 1, 2026, 3:21 PM
Reserved
Aug 27, 2026, 11:12 AM
Status
Analyzed
Published
Aug 27, 2026, 5:21 PM
Modified
Sep 1, 2026, 6:13 PM