CVE-2026-81719 openssl_encrypt before 1.4.9 Remote Code Execution via Plugin

Critical 9.3 Published 27 Aug 2026 Updated 1 Oct 2026

Attackers can achieve arbitrary code execution by inducing users to load malicious plugins due to insufficient signature enforcement and bypassable AST checks.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2026-81719?

CVE-2026-81719 is a critical code injection vulnerability in Jahlives Openssl Encrypt, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

openssl_encrypt before 1.4.9 executes untrusted third-party plugins with insufficient controls: the plugin signature policy defaulted to WARN, so an unsigned/unverifiable non-built-in plugin was compiled and executed in the host process at import time, before the runtime sandbox is installed. The only default gate was an incomplete, bypassable AST denylist. If a user is induced to load an attacker's plugin, this results in arbitrary code execution with the privileges of the user running openssl_encrypt. Fixed in 1.4.9 by defaulting the signature policy to ENFORCE for non-built-in plugins.

Weakness: CWE-94

Which versions are affected by CVE-2026-81719?

1 open source package ship an affected version, including openssl-encrypt. It affects 1 product.

Package	Affected	Fixed in
`openssl-encrypt` PyPI	All versions	`1.4.9`

Products include Jahlives Openssl Encrypt.

How do I fix CVE-2026-81719?

Upgrade openssl-encrypt to 1.4.9 or later.

Upgrade, and never evaluate templates, expressions or code built from user input. More about Code injection.

Is CVE-2026-81719 being exploited?

There is no known exploitation of CVE-2026-81719 in the wild and no public exploit code.

All Jahlives Openssl Encrypt vulnerabilities

Sources

Also known as GHSA-587j-4r3v-cm2c, GHSA-chrm-8mrh-xgj7, PYSEC-2026-3802.