CVE-2026-41564: CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking. The Crypt::PK::RS

Q: How do I fix CVE-2026-41564?

cryptx: upgrade to 0.088. Exact commands for each OS are on this page.

Q: Is CVE-2026-41564 being exploited?

CVE-2026-41564 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-41564 affect?

CVE-2026-41564 affects cryptx. Severity is high (CVSS 7.5). 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

Q: How urgent is CVE-2026-41564?

Priority 41/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2026-41564 is a high-severity flaw (CVSS 7.5) affecting cryptx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 pr

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-335, CWE-338
Published	2026-04-23
Last modified	2026-10-26

Publisher (CNA): CPANSec · Vendor: dcit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-23 08:16 UTCPublished CVE record published
2026-10-26 22:10 UTCUpdated Record last modified

dcit cryptx UPGRADE

Affected: < 0.088

Fixed in: 0.088

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy cryptx || rpm -q cryptx || cryptx --version

2. UPGRADE to 0.088 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade cryptx

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade cryptx

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41564?

cryptx: upgrade to 0.088. Exact commands for each OS are on this page.

Is CVE-2026-41564 being exploited?

CVE-2026-41564 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41564 affect?

CVE-2026-41564 affects cryptx. Severity is high (CVSS 7.5). 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

How urgent is CVE-2026-41564?

Priority 41/100. High severity; Remotely exploitable, no login, no user action

Software pages

Perl vulnerabilities

References

← Back to latest CVEs