openssl_encrypt versions before 1.4.0 contain an arbitrary code execution vulnerability in the Whirlpool hash implementation that uses broad glob patterns to load .so modules without integrity verification. Attackers can place malicious .so files matching the whirlpool*py313*.so pattern in site-packages directories to achieve native code execution when the module is loaded.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-74872 represents a critical arbitrary code execution vulnerability in openssl_encrypt versions before 1.4.0, stemming from unsafe dynamic module loading in the Whirlpool hash implementation. The vulnerability exploits broad glob patterns that load .so (shared object) files without integrity verification, allowing attackers to inject malicious native libraries into Python environments. Any system using vulnerable openssl_encrypt versions is at risk, particularly Python applications that rely on this cryptographic library for hashing operations. The attack surface is especially concerning because site-packages directories are often writable by multiple users or automated processes, making them attractive targets for privilege escalation and supply chain attacks.
While this CVE doesn't map directly to existing MITRE ATT&CK techniques in current frameworks, Casky's extended reasoning capabilities would identify the underlying attack patterns as variants of T1574 (Hijacking Execution Flow) and T1195 (Supply Chain Compromise). Practitioners using Casky would observe detection signals around suspicious .so file creation in site-packages matching the whirlpool*py313*.so pattern, unsigned or unverified module loading attempts, and unexpected process execution originating from Python interpreters. Casky's Claude-powered analysis would correlate these indicators with the module loading behavior and flag the absence of cryptographic integrity checks as a critical gap, enabling security teams to proactively identify compromised environments before native code execution occurs.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-74872. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation