CVE-2026-41564

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

CVE-2026-41564 is fixed in 5 products on 1 platform, first by ALAS2023-2026-1641, released May 11, 2026. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.5
high
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0043
37th 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.

Where it's fixed

ProductFixed inFixReleased
Linux
libcryptx-perl · Debian 13.5 (trixie) 0.085-1+deb13u1 DEBIAN-CVE-2026-41564 May 15, 2026
libcryptx-perl · Debian 14 0.087-2 DEBIAN-CVE-2026-41564 May 15, 2026
perl-CryptX · amzn 2023 0.088-2.amzn2023.0.1 ALAS2023-2026-1641 May 11, 2026
perl-CryptX · opensuse-leap 16.0 0.89.0-bp160.1.1 OPENSUSE-SU-2026:20936-1 Jun 10, 2026
perl-CryptX-debuginfo · amzn 2023 0.088-2.amzn2023.0.1 ALAS2023-2026-1641 May 11, 2026
perl-CryptX-debugsource · amzn 2023 0.088-2.amzn2023.0.1 ALAS2023-2026-1641 May 11, 2026
perl-CryptX-tests · amzn 2023 0.088-2.amzn2023.0.1 ALAS2023-2026-1641 May 11, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.