Sandbox bypass via unsandboxed process worker
Published Aug 17, 2026 · Updated Aug 17, 2026
Sandbox bypass in jahlives openssl_encrypt before 1.4.0 allows attackers to run plugins without sandbox controls via process isolation. In openssl_encrypt/modules/plugin_system/plugin_sandbox.py, the default multiprocessing _plugin_worker path calls plugin.execute(context) directly and omits sandbox setup, the PluginImportGuard, and the file, network, process, and resource restrictions applied in the non-default threading path. Reachability depends on a deployment that accepts attacker-supplied plugins; once such a plugin is launched in the default mode, it gains filesystem, network, subprocess, and unrestricted Python module access instead of the intended sandbox.
Summary
What happened
Sandbox bypass in jahlives openssl_encrypt before 1.4.0 allows attackers to run plugins without sandbox controls via process isolation. In openssl_encrypt/modules/plugin_system/plugin_sandbox.py, the default multiprocessing _plugin_worker path calls plugin.execute(context) directly and omits sandbox setup, the PluginImportGuard, and the file, network, process, and resource restrictions applied in the non-default threading path. Reachability depends on a deployment that accepts attacker-supplied plugins; once such a plugin is launched in the default mode, it gains filesystem, network, subprocess, and unrestricted Python module access instead of the intended sandbox.
The record
- CVE
- CVE-2026-74895
- Published
- Aug 17, 2026
- Updated
- Aug 17, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-693
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 17, 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.0
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