CVE-2026-41564
7.5MIK · CryptX
CryptX versions before 0.088 fail to reseed the PRNG state after forking, which can lead to identical random outputs and private key recovery across child processes.
Executive summary
A critical cryptographic vulnerability in the MIK CryptX Perl module allows for private key recovery due to improper PRNG seeding after process forking.
Vulnerability
The vulnerability stems from improper usage of seeds in a pseudo-random number generator, specifically failing to detect process forks. This allows an unauthenticated attacker to recover private keys by analyzing identical signatures produced by child processes that inherited a shared PRNG state.
Business impact
The compromise of private cryptographic keys represents a catastrophic failure of security controls. If an attacker recovers these keys, they can decrypt sensitive communications, forge digital signatures, and impersonate services, leading to severe data breaches and loss of system integrity. The CVSS score of 7.5 reflects the high risk to confidentiality, particularly for services utilizing preforking architectures like Starman.
Remediation
Immediate Action: Upgrade to CryptX version 0.088 or later immediately to ensure proper PRNG reseeding. Existing private keys generated or used by objects created before a fork on previous versions must be considered compromised and should be rotated.
Proactive Monitoring: Review application logs for unusual cryptographic errors or repeated signature patterns that might indicate exploitation attempts. Audit environments using preforking web servers to identify services that rely on the Crypt::PK modules.
Compensating Controls: Ensure that all cryptographic operations are performed within isolated process contexts where possible. Limit the exposure of long-lived keys by restricting their usage to processes that perform explicit re-seeding or utilize hardware security modules.
Exploitation status
Public Exploit Available: Unknown.
Analyst recommendation
Given the potential for complete cryptographic failure, organizations must prioritize upgrading the CryptX library. Because this vulnerability affects the fundamental security of generated keys, administrators should assume that any keys handled by affected versions are compromised and must initiate a formal key rotation procedure following the software update.