Code execution via unverified Whirlpool module load
Published Aug 17, 2026 · Updated Aug 18, 2026
Arbitrary code execution in jahlives OpenSSL Encrypt before 1.4.0 allows attackers to run native code via a malicious Whirlpool module. In openssl_encrypt/modules/registry/hash_registry.py, the Whirlpool loader globs for whirlpoolpy313.so in site-packages and executes the first match through importlib without checking that the file is trusted. Exploitation requires a way to place a matching shared object in a searched site-packages path; the result is code execution in the application's process context.
Summary
What happened
Arbitrary code execution in jahlives OpenSSL Encrypt before 1.4.0 allows attackers to run native code via a malicious Whirlpool module. In openssl_encrypt/modules/registry/hash_registry.py, the Whirlpool loader globs for whirlpoolpy313.so in site-packages and executes the first match through importlib without checking that the file is trusted. Exploitation requires a way to place a matching shared object in a searched site-packages path; the result is code execution in the application's process context.
The record
- CVE
- CVE-2026-74872
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- jahlives
- Product
- OpenSSL Encrypt
- Classifications
- CWE-426, T1574.006
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 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.
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