Bug 2461076 (CVE-2026-41564) - CVE-2026-41564 perl-cryptx: CryptX: Private key recovery due to predictable pseudo-random number generation after forking
Summary: CVE-2026-41564 perl-cryptx: CryptX: Private key recovery due to predictable p...
Keywords:
Status: NEW
Alias: CVE-2026-41564
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2461084 2461085
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-23 08:01 UTC by OSIDB Bzimport
Modified: 2026-04-23 09:46 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-04-23 08:01:25 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.