Is CVE-2026-81719 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-81719 being exploited in the wild.

How severe is CVE-2026-81719?

High severity, with a CVSS score of 7.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-81719?

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-81719 attacked?

It is attacked with local access.

Am I affected by CVE-2026-81719?

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.

CVE-2026-81719: openssl_encrypt arbitrary code execution via plugin signature bypass

CVE-2026-81719 · Severity: high · CVSS 7.8 · Published 2026-08-27

openssl_encrypt is a Python library used for encryption operations. A critical vulnerability allows untrusted third-party plugins to execute arbitrary code with user privileges when loaded, because the signature verification policy defaulted to WARN instead of ENFORCE. If an attacker tricks a user into loading a malicious plugin, the attacker gains full control of the user's system and all data accessible to that user.

Technologies: Jahlives Openssl Encrypt, openssl-encrypt (PyPI). Vendors: Jahlives, PyPI.

Quick answers

Is CVE-2026-81719 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-81719 being exploited in the wild.
How severe is CVE-2026-81719?: High severity, with a CVSS score of 7.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-81719?: 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-81719 attacked?: It is attacked with local access.
Am I affected by CVE-2026-81719?: 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
```
pip install "openssl-encrypt>=1.4.9"
```

Technical details

The vulnerability is a code injection flaw (CWE-94) in openssl_encrypt's plugin loading mechanism. When a non-built-in plugin is imported at runtime, the library compiles and executes it in the host process before the runtime sandbox is installed. The signature policy defaulted to WARN, meaning unsigned or unverifiable plugins were executed anyway, with only an incomplete and bypassable AST denylist as protection. An attacker can craft a malicious plugin that, when imported by a user, executes arbitrary code with the full privileges of the running process. The vulnerability requires user interaction (inducing the user to load the plugin) but no authentication. Fixed in version 1.4.9 by changing the default signature policy to ENFORCE, requiring plugin signatures to be verified before execution.

Affected products

jahlives openssl_encrypt before 1.4.9

Identifiers

CVE-2026-81719
PYSEC-2026-3802

Timeline

2026-08-12: disclosed
2026-08-27: advisory
2026-08-27: patched: Version 1.4.9 released with signature policy default changed to ENFORCE

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.