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

High 8.7 Published Updated

A path traversal flaw in the openssl_encrypt library allows sandboxed plugins to bypass isolation and read or write files in other plugin directories.

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

CVE-2026-81716 is a high-severity path traversal 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 (pip: openssl-encrypt) versions before 1.4.9 contain a path traversal flaw in PluginSandbox._is_safe_path, which authorized file access using a bare string-prefix match. A sandboxed plugin without the READ_FILES 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.

Weakness: CWE-22

Which versions are affected by CVE-2026-81716?

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

PackageAffectedFixed in
openssl-encrypt PyPIAll versions1.4.9

Products include Jahlives Openssl Encrypt.

How do I fix CVE-2026-81716?

Upgrade openssl-encrypt to 1.4.9 or later.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-81716 being exploited?

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

All Jahlives Openssl Encrypt vulnerabilities

Sources

Also known as GHSA-7qxw-7jv4-3qr8, GHSA-vr4h-5xqv-xxxf, PYSEC-2026-3800.

Is CVE-2026-81716 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free