CVE-2026-41564
published 2026-04-23CVE-2026-41564: 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…
PriorityP344high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
EPSS
0.45%
35.7th percentile
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.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| dcit | cryptx | < 0.088 | 0.088 |
| mik | cryptx | < 0.088 | 0.088 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
No advisories linked to this vulnerability.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-41564 perl-CryptX: CryptX: Private key recovery due to predictable pseudo-random number generation after forking [epel-all]
bugzilla·2026-04-23·CVSS 7.5
CVE-2026-41564 [HIGH] CVE-2026-41564 perl-CryptX: CryptX: Private key recovery due to predictable pseudo-random number generation after forking [epel-all]
CVE-2026-41564 perl-CryptX: CryptX: Private key recovery due to predictable pseudo-random number generation after forking [epel-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Discussion:
FEDORA-EPEL-2026-401e78e90b (perl-CryptX-0.088-2.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-401e78e90b
---
FEDORA-EPEL-2026-25a3af10b3 (perl-CryptX-0.088-2.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-25a3af10b3
---
FEDORA-EPEL-2026-6bff23a642 (perl-CryptX-0.088-2.el8) has been sub
Bugzilla
CVE-2026-41564 perl-cryptx: CryptX: Private key recovery due to predictable pseudo-random number generation after forking
bugzilla·2026-04-23·CVSS 7.5
CVE-2026-41564 [HIGH] CVE-2026-41564 perl-cryptx: CryptX: Private key recovery due to predictable pseudo-random number generation after forking
CVE-2026-41564 perl-cryptx: CryptX: Private key recovery due to predictable pseudo-random number generation after forking
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 th
Bugzilla
CVE-2026-41564 perl-CryptX: CryptX: Private key recovery due to predictable pseudo-random number generation after forking [fedora-all]
bugzilla·2026-04-23·CVSS 7.5
CVE-2026-41564 [HIGH] CVE-2026-41564 perl-CryptX: CryptX: Private key recovery due to predictable pseudo-random number generation after forking [fedora-all]
CVE-2026-41564 perl-CryptX: CryptX: Private key recovery due to predictable pseudo-random number generation after forking [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Discussion:
FEDORA-2026-bc5090f99b (perl-CryptX-0.088-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-bc5090f99b
---
FEDORA-2026-3e1f671a17 (perl-CryptX-0.088-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-3e1f671a17
---
FEDORA-2026-f533fcc0b6 has been pushed to the Fedora 44 testing repository.
Soon you'll be able
https://github.com/DCIT/perl-CryptX/commit/9a1dd3e0c27d68e32450be5538b864c2b115ee15.patchhttps://github.com/DCIT/perl-CryptX/security/advisories/GHSA-24c2-gp6c-24c6https://metacpan.org/release/MIK/CryptX-0.088http://www.openwall.com/lists/oss-security/2026/04/23/2https://github.com/DCIT/perl-CryptX/security/advisories/GHSA-24c2-gp6c-24c6
2026-04-23
Published