# CVE-2026-81700: openssl_encrypt GPG signature verification bypass in gpg_runner

Source: https://junglewise.ai/threats/cve-2026-81700-openssl-encrypt-gpg-signature-verification-bypass-in-gpg-runner  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-27. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-81700 · Severity: critical · CVSS 9.8 · Published 2026-08-27

openssl_encrypt is a library that verifies cryptographic signatures on plugins and package manifests before execution. A flaw in the signature verification logic allows attackers with revoked or expired signing keys to bypass verification and execute malicious code in the host process, potentially compromising systems that rely on this library for secure plugin loading.

Technologies: [Jahlives Openssl Encrypt](https://junglewise.ai/threats/technologies/openssl-encrypt), [openssl-encrypt (PyPI)](https://junglewise.ai/threats/technologies/pypi-openssl-encrypt). Vendors: [Jahlives](https://junglewise.ai/threats/vendors/jahlives), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2026-81700 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-81700 being exploited in the wild.

**How severe is CVE-2026-81700?** Critical severity, with a CVSS score of 9.8, published 27 August 2026.

**Which products and versions are affected?** Jahlives Openssl Encrypt before 1.4.9; openssl-encrypt (PyPI) ECOSYSTEM:introduced=0,fixed=1.4.9.

**Is there a fix for CVE-2026-81700?** Yes. openssl-encrypt (PyPI): upgrade to 1.4.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-81700 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-81700?** Check whether you run Jahlives Openssl Encrypt or openssl-encrypt (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- openssl-encrypt (PyPI): upgrade to 1.4.9 or later

  ```sh
  pip install "openssl-encrypt>=1.4.9"
  ```


## Technical details

The vulnerability is an improper cryptographic signature verification (CWE-347) in the gpg_runner.verify_detached function. The root cause is insufficient inspection of GnuPG status output: the code checks only for VALIDSIG/GOODSIG without examining REVKEYSIG, EXPKEYSIG, EXPSIG, or the gpg exit code. This allows cryptographically valid signatures made with revoked or expired keys to be accepted. Additionally, the fingerprint validation compared the subkey fingerprint rather than the primary key fingerprint. The attack requires the attacker to possess a signing key that was previously valid and is now revoked or expired. Exploitation results in arbitrary code execution in the host process. The fix in version 1.4.9 requires both GOODSIG and VALIDSIG, treats revocation/expiration status flags as failures, checks the gpg exit code, and compares the primary-key fingerprint.

## Affected products

- jahlives openssl_encrypt before 1.4.9

## Identifiers

- CVE-2026-81700
- PYSEC-2026-3777

## Timeline

- 2026-08-12: disclosed
- 2026-08-12: patched: Version 1.4.9 released with fix
- 2026-08-27: advisory

## References

- [https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-x38r-8wf3-q9hq](https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-x38r-8wf3-q9hq)
- [https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-gpg-signature-verification-bypass](https://www.vulncheck.com/advisories/openssl-encrypt-before-1.4.9-gpg-signature-verification-bypass)

## Related threats

- [openssl_encrypt KDF cost parameter validation bypass](https://junglewise.ai/threats/cve-2026-81721-openssl-encrypt-kdf-cost-parameter-validation-bypass)
- [openssl_encrypt memory exhaustion in identity file protection block](https://junglewise.ai/threats/cve-2026-81720-openssl-encrypt-memory-exhaustion-in-identity-file-protection)
- [openssl_encrypt arbitrary code execution via plugin signature bypass](https://junglewise.ai/threats/cve-2026-81719-openssl-encrypt-arbitrary-code-execution-via-plugin-signature)
- [openssl_encrypt weak PBKDF2 parameters in keyfile encryption](https://junglewise.ai/threats/cve-2026-81718-openssl-encrypt-weak-pbkdf2-parameters-in-keyfile-encryption)
- [openssl_encrypt USB drive integrity bypass with fixed KDF salt](https://junglewise.ai/threats/cve-2026-81717-openssl-encrypt-usb-drive-integrity-bypass-with-fixed-kdf-salt)
