CVE-2026-41564

published 23 Apr 2026 · updated 23 Apr 2026

CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking

7.5HighCVSS 7.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 0.088.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
MIK<0.0880.088

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-41564 severity on Zeptric[![CVE-2026-41564](https://zeptric.io/badge/cve/CVE-2026-41564.svg)](https://zeptric.io/cve/CVE-2026-41564)