{"api_version":"1","generated_at":"2026-04-23T10:58:30+00:00","cve":"CVE-2026-41564","urls":{"html":"https://cve.report/CVE-2026-41564","api":"https://cve.report/api/cve/CVE-2026-41564.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-41564","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-41564"},"summary":{"title":"CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking","description":"CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking.\n\nThe 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.\n\nThis affects preforking services such as the Starman web server, where a Crypt::PK::* object loaded at startup is inherited by every worker process.","state":"PUBLISHED","assigner":"CPANSec","published_at":"2026-04-23 08:16:01","updated_at":"2026-04-23 10:16:17"},"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)"],"metrics":[],"references":[{"url":"https://github.com/DCIT/perl-CryptX/commit/9a1dd3e0c27d68e32450be5538b864c2b115ee15.patch","name":"https://github.com/DCIT/perl-CryptX/commit/9a1dd3e0c27d68e32450be5538b864c2b115ee15.patch","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://metacpan.org/release/MIK/CryptX-0.088","name":"https://metacpan.org/release/MIK/CryptX-0.088","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"http://www.openwall.com/lists/oss-security/2026/04/23/2","name":"http://www.openwall.com/lists/oss-security/2026/04/23/2","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://github.com/DCIT/perl-CryptX/security/advisories/GHSA-24c2-gp6c-24c6","name":"https://github.com/DCIT/perl-CryptX/security/advisories/GHSA-24c2-gp6c-24c6","refsource":"9b29abf9-4ab0-4765-b253-1875cd9b441e","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-41564","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-41564","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"MIK","product":"CryptX","version":"affected 0.088 custom","platforms":[]}],"timeline":[{"source":"CNA","time":"2026-04-18T00:00:00.000Z","lang":"en","value":"Issue discovered."},{"source":"CNA","time":"2026-04-21T00:00:00.000Z","lang":"en","value":"Reported to upstream maintainer."},{"source":"CNA","time":"2026-04-23T00:00:00.000Z","lang":"en","value":"CryptX 0.088 released with fix."}],"solutions":[{"source":"CNA","title":"","value":"Upgrade to CryptX 0.088 or later, or apply the upstream patch.\n\nApplying 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.","time":"","lang":"en"}],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"providerMetadata":{"dateUpdated":"2026-04-23T09:33:41.857Z","orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE"},"references":[{"url":"http://www.openwall.com/lists/oss-security/2026/04/23/2"}],"title":"CVE Program Container"}],"cna":{"affected":[{"collectionURL":"https://cpan.org/modules","defaultStatus":"unaffected","packageName":"CryptX","product":"CryptX","programFiles":["inc/CryptX_PK_RSA.xs.inc","inc/CryptX_PK_DSA.xs.inc","inc/CryptX_PK_DH.xs.inc","inc/CryptX_PK_ECC.xs.inc","inc/CryptX_PK_Ed25519.xs.inc","inc/CryptX_PK_X25519.xs.inc"],"repo":"https://github.com/DCIT/perl-CryptX","vendor":"MIK","versions":[{"lessThan":"0.088","status":"affected","version":"0","versionType":"custom"}]}],"descriptions":[{"lang":"en","value":"CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking.\n\nThe 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.\n\nThis affects preforking services such as the Starman web server, where a Crypt::PK::* object loaded at startup is inherited by every worker process."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-335","description":"CWE-335 Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)","lang":"en","type":"CWE"}]},{"descriptions":[{"cweId":"CWE-338","description":"CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2026-04-23T07:29:26.340Z","orgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","shortName":"CPANSec"},"references":[{"tags":["vendor-advisory"],"url":"https://github.com/DCIT/perl-CryptX/security/advisories/GHSA-24c2-gp6c-24c6"},{"tags":["patch"],"url":"https://github.com/DCIT/perl-CryptX/commit/9a1dd3e0c27d68e32450be5538b864c2b115ee15.patch"},{"tags":["release-notes"],"url":"https://metacpan.org/release/MIK/CryptX-0.088"}],"solutions":[{"lang":"en","value":"Upgrade to CryptX 0.088 or later, or apply the upstream patch.\n\nApplying 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."}],"source":{"discovery":"UNKNOWN"},"timeline":[{"lang":"en","time":"2026-04-18T00:00:00.000Z","value":"Issue discovered."},{"lang":"en","time":"2026-04-21T00:00:00.000Z","value":"Reported to upstream maintainer."},{"lang":"en","time":"2026-04-23T00:00:00.000Z","value":"CryptX 0.088 released with fix."}],"title":"CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking","x_generator":{"engine":"cpansec-cna-tool 0.1"}}},"cveMetadata":{"assignerOrgId":"9b29abf9-4ab0-4765-b253-1875cd9b441e","assignerShortName":"CPANSec","cveId":"CVE-2026-41564","datePublished":"2026-04-23T07:29:26.340Z","dateReserved":"2026-04-21T12:45:20.132Z","dateUpdated":"2026-04-23T09:33:41.857Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-04-23 08:16:01","lastModifiedDate":"2026-04-23 10:16:17","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)"],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"41564","Ordinal":"1","Title":"CryptX versions before 0.088 for Perl do not reseed the Crypt::P","CVE":"CVE-2026-41564","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"41564","Ordinal":"1","NoteData":"CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking.\n\nThe 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.\n\nThis affects preforking services such as the Starman web server, where a Crypt::PK::* object loaded at startup is inherited by every worker process.","Type":"Description","Title":"CryptX versions before 0.088 for Perl do not reseed the Crypt::P"}]}}}