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

Published Aug 27, 2026
·
Updated

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.

Affected Software

1 affected component
OpenSSL openssl_encrypt<1.4.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openssl_encrypt to a version that resolves this vulnerability.

    Fixed in 1.4.9
  2. Configuration

    In openssl_encrypt v1.4.9, default the plugin signature policy to ENFORCE for non-built-in plugins so unsigned/unverifiable non-built-in plugins are not compiled/executed.

    openssl_encrypt plugin signature policy = ENFORCE for non-built-in plugins
  3. Compensating control

    Ensure users cannot load attacker-controlled plugins (e.g., restrict or vet which non-built-in plugins are allowed to be installed/loaded), since inducing a user to load an attacker's plugin can lead to arbitrary code execution.

Event History

Aug 27, 2026
CVE Published
via MITRE·02:51 PM
Data Sourced
via MITRE·02:51 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:21 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is exposed to exploitation?

Users running versions before 1.4.9 are exposed if they can be induced to load an attacker-controlled third-party plugin. Code runs with the privileges of the user running openssl_encrypt.

2

Are default settings affected?

Yes. Before 1.4.9, the default signature policy was WARN, which allowed unsigned or unverifiable non-built-in plugins to be compiled and executed. The remaining default AST denylist was incomplete and bypassable.

3

What changed in the fix?

Version 1.4.9 changes the default signature policy to ENFORCE for non-built-in plugins. This prevents the prior default behavior of accepting unsigned or unverifiable third-party plugins.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203