CVE-2026-81716: openssl_encrypt before 1.4.9 Plugin Sandbox Path Traversal

Published Aug 27, 2026
·
Updated

opensslencrypt (pip: openssl-encrypt) versions before 1.4.9 contain a path traversal flaw in PluginSandbox.issafepath, which authorized file access using a bare string-prefix match. A sandboxed plugin without the READFILES permission could read or write another plugin's directory that merely shares a name prefix (e.g., .../plugins/foobar matching allowed .../plugins/foo), breaking per-plugin isolation within the same user. Fixed by matching each allowed directory exactly or with a trailing path separator.

Affected Software

1 affected component
openssl_encrypt openssl_encrypt (pip: openssl-encrypt)<1.4.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openssl_encrypt (pip: openssl-encrypt) to a version that resolves this vulnerability.

    Fixed in 1.4.9
  2. Configuration

    Update the plugin sandbox path validation logic so allowed directories are matched exactly or only when the candidate path starts with the allowed directory followed by a trailing path separator (avoid bare string-prefix matching).

    PluginSandbox._is_safe_path Allowed directory matching = Exact directory match or prefix match only with trailing path separator

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 this issue?

Installations running versions before 1.4.9 are exposed when sandboxed plugins run under the same user and plugin directories have overlapping name prefixes, such as foo and foobar.

2

What does an attacker need to exploit it?

An attacker needs control of a sandboxed plugin. The plugin does not need the READ_FILES permission if it can target another plugin directory whose path shares a bare prefix with an allowed directory.

3

What is the impact within an affected deployment?

A malicious plugin may read or write files in another plugin's directory despite per-plugin sandbox isolation. The issue does not describe access outside the same user's plugin directories.

4

What can be done before upgrading?

Avoid plugin directory names where one name is a prefix of another, and do not run untrusted sandboxed plugins alongside plugins whose files must remain isolated. Upgrade to version 1.4.9 or later when possible.

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