CVE-2026-41564 CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking
Attackers can recover private keys from preforking services due to shared PRNG state after forking in the CryptX Perl library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-41564?
CVE-2026-41564 is a high-severity vulnerability in MIK CryptX, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-41564?
It affects 1 product.
Linux distribution packages (1)
perl-CryptX openSUSE:Tumbleweed | All versions | 0.89.0-1.1 |
Products include Dcit Cryptx.
How do I fix CVE-2026-41564?
Upgrade to a fixed version.
Is CVE-2026-41564 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41564 exists.
Sources
Also known as ALPINE-CVE-2026-41564, DEBIAN-CVE-2026-41564, GHSA-24c2-gp6c-24c6, UBUNTU-CVE-2026-41564, openSUSE-SU-2026:10773-1.