opensslencrypt 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 opensslencrypt. Fixed in 1.4.9 by defaulting the signature policy to ENFORCE for non-built-in plugins.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/81xxx/CVE-2026-81719.json",
"cwe_ids": [
"CWE-94"
],
"cna_assigner": "VulnCheck"
}