CVE-2026-41564 Affecting perl-cryptx package, versions <0.088-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ALPINE320-PERLCRYPTX-17074619
- published29 May 2026
- disclosed23 Apr 2026
Introduced: 23 Apr 2026
CVE-2026-41564 (opens in a new tab)How to fix?
Upgrade Alpine:3.20 perl-cryptx to version 0.088-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl-cryptx package and not the perl-cryptx package as distributed by Alpine.
See How to fix? for Alpine:3.20 relevant fixed versions and status.
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.