How severe is CVE-2026-41564?

CVE-2026-41564 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2026-41564 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-41564?

CVE-2026-41564 affects Dcit Cryptx. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-41564?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-41564 have an EU (EUVD) identifier?

Yes. CVE-2026-41564 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25201.

When was CVE-2026-41564 published?

CVE-2026-41564 was published on 2026-04-23 and last updated on 2026-06-17.

CVE-2026-41564

CVE-2026-41564 is a high-severity vulnerability in Dcit Cryptx with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-335.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (36th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-25201
Weakness: CWE-335
Affected product: Dcit Cryptx
Published: 2026-04-23
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2026-41564?: 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.
How severe is CVE-2026-41564?: CVE-2026-41564 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-41564 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-41564?: CVE-2026-41564 affects Dcit Cryptx. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-41564?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-41564 have an EU (EUVD) identifier?: Yes. CVE-2026-41564 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25201.
When was CVE-2026-41564 published?: CVE-2026-41564 was published on 2026-04-23 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:dcit:cryptx:*:*:*:*:*:perl:*:*

Other CWE-335 vulnerabilities

CVE-2024-36048 — Critical (CVSS 9.8): QAbstractOAuth in Qt Network Authorization in Qt before 5.15.17, 6.x before 6.2.13, 6.3.x through 6.5.x before 6.5.6,…
CVE-2023-4472 — Critical (CVSS 9.8): Objectplanet Opinio version 7.22 and prior uses a cryptographically weak pseudo-random number generator (PRNG) coupled…
CVE-2012-1577 — Critical (CVSS 9.8): lib/libc/stdlib/random.c in OpenBSD returns 0 when seeded with 0.
CVE-2019-11495 — Critical (CVSS 9.8): In Couchbase Server 5.1.1, the cookie used for intra-node communication was not generated securely. Couchbase Server…
CVE-2019-10908 — Critical (CVSS 9.8): In Airsonic 10.2.1, RecoverController.java generates passwords via org.apache.commons.lang.RandomStringUtils, which…
CVE-2017-11519 — Critical (CVSS 9.8): passwd_recovery.lua on the TP-Link Archer C9(UN)_V2_160517 allows an attacker to reset the admin password by leveraging…

Browse all CWE-335 vulnerabilities →