Is CVE-2026-81716 exploited in the wild?

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

How severe is CVE-2026-81716?

Medium severity, with a CVSS score of 5.2, 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-81716?

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

It is attacked with local access.

Am I affected by CVE-2026-81716?

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-81716: openssl-encrypt path traversal in PluginSandbox

CVE-2026-81716 · Severity: medium · CVSS 5.2 · Published 2026-08-27

openssl-encrypt is a Python library providing sandboxed plugin execution with file access restrictions. A flaw in the sandbox path validation allows plugins without READ_FILES permission to access sibling plugins' directories by exploiting a bare string-prefix match, compromising isolation between plugins running under the same user and potentially exposing sensitive plugin data.

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

Quick answers

Is CVE-2026-81716 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-81716 being exploited in the wild.
How severe is CVE-2026-81716?: Medium severity, with a CVSS score of 5.2, 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-81716?: 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-81716 attacked?: It is attacked with local access.
Am I affected by CVE-2026-81716?: 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 path traversal flaw in PluginSandbox._is_safe_path that performs a bare string-prefix match when authorizing file access, rather than validating complete directory paths. An attacker controlling a sandboxed plugin without the READ_FILES permission can craft a path that shares a name prefix with an allowed directory (e.g., accessing /plugins/foobar when /plugins/foo is whitelisted) to read or write files in another plugin's directory. This breaks the security model's per-plugin isolation guarantee. The fix validates each allowed directory as a complete match or with a trailing path separator. Patch available in version 1.4.9.

Affected products

jahlives openssl-encrypt before 1.4.9

Identifiers

CVE-2026-81716
PYSEC-2026-3800

Timeline

2026-08-27: disclosed: Vulnerability disclosed
2026-08-12: patched: Fixed in version 1.4.9

References

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