Cross-plugin file access via bare path prefix
Published Aug 27, 2026 · Updated Aug 27, 2026
Path traversal in jahlives OpenSSL Encrypt before 1.4.9 allows local users to read or write sibling plugin files. PluginSandbox._is_safe_path accepts any resolved path whose string begins with an allowed directory, without requiring a path-separator boundary. Exploitation requires control of a sandboxed plugin and a sibling directory with a shared name prefix, bypassing per-plugin isolation within the same user.
Summary
What happened
Path traversal in jahlives OpenSSL Encrypt before 1.4.9 allows local users to read or write sibling plugin files. PluginSandbox._is_safe_path accepts any resolved path whose string begins with an allowed directory, without requiring a path-separator boundary. Exploitation requires control of a sandboxed plugin and a sibling directory with a shared name prefix, bypassing per-plugin isolation within the same user.
The record
- CVE
- CVE-2026-81716
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-22, T1005, T1565.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.4.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo