CVE-2026-41564
CryptX versions before 0.088 for Perl do not reseed the Crypt::PK …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/DCIT/perl-CryptX/commit/9a1dd3e0c27d68e32450be5538b864c2b115ee15.patch
- github.com/DCIT/perl-CryptX/security/advisories/GHSA-24c2-gp6c-24c6
- metacpan.org/release/MIK/CryptX-0.088
- www.openwall.com/lists/oss-security/2026/04/23/2
- nvd.nist.gov/vuln/detail/CVE-2026-41564
- cve.org/CVERecord?id=CVE-2026-41564
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.