A HIGH-severity vulnerability identified as CVE-2026-41564 has been published on April 23, 2026 with a CVSS base score of 7.5. This security advisory provides a detailed breakdown of the vulnerability, its potential impact, weakness classification, and actionable steps to protect your systems.
Table of Contents
ToggleVulnerability Details
CVE ID: CVE-2026-41564
Severity: HIGH
CVSS Score: 7.5
Published: April 23, 2026
Weakness (CWE): CWE-335
| Attack Vector | Network |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
| Confidentiality Impact | High |
| Integrity Impact | None |
| Availability Impact | None |
Technical 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.
Potential Impact
If exploited, this high-severity vulnerability could allow an attacker to compromise sensitive data confidentiality. Organizations running affected software should treat this as a priority remediation item.
Recommended Action
No official patch is available yet. Until one is released:
- Monitor the official NVD page and vendor channels for patch announcements.
- Restrict access to the affected system or service where possible.
- Apply network-level mitigations such as firewall rules or WAF policies.
- Enable logging and alerting for anomalous activity related to this vulnerability.
- Review your incident response plan in case of active exploitation.
References
Related Security Advisories
- [HIGH] CVE-2026-3259 — CVSS 7.1 (April 23, 2026) — HIGH / CVSS 7.1
- [HIGH] CVE-2026-6022 — CVSS 7.5 (April 22, 2026) — HIGH / CVSS 7.5
- [HIGH] CVE-2026-6023 — CVSS 8.1 (April 22, 2026) — HIGH / CVSS 8.1

![[HIGH] CVE-2020-37227 — CVSS 8.8 (May 16, 2026)](https://atlas-cybersecurity.com/wp-content/plugins/elementor/assets/images/placeholder.png)



