CVE-2026-41564

High

Published: 23/04/2026(UTC)Translated: 15/06/2026(UTC)NVD NIST

Summary

CryptX versions before 0.088 for Perl do not reseed the PRNG state after forking. Crypt::PK::* objects created before `fork()` share identical PRNG state with every child process, which can lead to identical outputs for randomized operations, including key generation.

Risk Assessment

Organizations using preforking services, such as the Starman web server, are at risk of exposing private keys through nonce reuse, potentially leading to security compromises.

Recommendation

It is recommended to upgrade to CryptX version 0.088 or later to ensure proper reseeding of the PRNG state after forking. Additionally, consider reviewing the application architecture to minimize risks associated with shared PRNG state.

Other vulnerabilities in CryptX

CVE-2026-13758Low
A vulnerability in CryptX versions before 0.088_001 for Perl causes AEAD authentication tag comparison in the decrypt_done path to be non-constant time. The decrypt_done($tag) function uses memNE (memcmp() != 0), which short-circuits on the first differing byte, making execution time depend on the number of matching leading bytes.

Original NVD description (English source)

CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking. The Crypt::PK::RSA, Crypt::PK::DSA, Crypt::PK::DH, Crypt::PK::ECC, Crypt::PK::Ed25519 and Crypt::PK::X25519 modules seed a per-object PRNG state in their constructors and reuse it without fork detection. A Crypt::PK::* object created before `fork()` shares byte-identical PRNG state with every child process, and any randomized operation they perform can produce identical output, including key generation. Two ECDSA or DSA signatures from different processes are enough to recover the signing private key through nonce-reuse key recovery. This affects preforking services such as the Starman web server, where a Crypt::PK::* object loaded at startup is inherited by every worker process.