CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking
Summary
| CVE | CVE-2026-41564 |
|---|---|
| State | PUBLISHED |
| Assigner | CPANSec |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-23 08:16:01 UTC |
| Updated | 2026-04-23 10:16:17 UTC |
| Description | 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. |
Risk And Classification
Problem Types: CWE-335 | CWE-338 | CWE-335 CWE-335 Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG) | CWE-338 CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| github.com/DCIT/perl-CryptX/commit/9a1dd3e0c27d68e32450be5538b864c2b115e... | 9b29abf9-4ab0-4765-b253-1875cd9b441e | github.com | |
| metacpan.org/release/MIK/CryptX-0.088 | 9b29abf9-4ab0-4765-b253-1875cd9b441e | metacpan.org | |
| www.openwall.com/lists/oss-security/2026/04/23/2 | af854a3a-2127-422b-91ae-364da2661108 | www.openwall.com | |
| github.com/DCIT/perl-CryptX/security/advisories/GHSA-24c2-gp6c-24c6 | 9b29abf9-4ab0-4765-b253-1875cd9b441e | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
Additional Advisory Data
| Source | Time | Event |
|---|---|---|
| CNA | 2026-04-18T00:00:00.000Z | Issue discovered. |
| CNA | 2026-04-21T00:00:00.000Z | Reported to upstream maintainer. |
| CNA | 2026-04-23T00:00:00.000Z | CryptX 0.088 released with fix. |
Solutions
CNA: Upgrade to CryptX 0.088 or later, or apply the upstream patch. Applying the fix does not retroactively protect keys that may already have been exposed. On an affected version, any private key used with or generated by a Crypt::PK::* object created before `fork()` should be assessed for rotation.
There are currently no legacy QID mappings associated with this CVE.