MIK CryptX up to 0.087 on Perl X25519 X25519 Modules prng seed

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.5$0-$5k4.82-

Summaryinfo

A vulnerability marked as problematic has been reported in MIK CryptX up to 0.087 on Perl. This affects the function Crypt::PK::RSA/Crypt::PK::DSA/Crypt::PK::DH/Crypt::PK::ECC/Crypt::PK::Ed25519/Crypt::PK::X25519 Modules of the component X25519 Module. This manipulation causes prng seed. This vulnerability is registered as CVE-2026-41564. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in MIK CryptX up to 0.087 on Perl. It has been declared as problematic. Affected by this vulnerability is the function Crypt::PK::RSA/Crypt::PK::DSA/Crypt::PK::DH/Crypt::PK::ECC/Crypt::PK::Ed25519/Crypt::PK::X25519 Modules of the component X25519 Module. The manipulation with an unknown input leads to a prng seed vulnerability. The CWE definition for the vulnerability is CWE-335. The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds. As an impact it is known to affect confidentiality. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-41564 since 04/21/2026. The exploitation appears to be difficult. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

Upgrading to version 0.088 eliminates this vulnerability. Applying the patch 9a1dd3e0c27d68e32450be5538b864c2b115ee15 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-25201). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.6
VulDB Meta Temp Score: 2.5

VulDB Base Score: 2.6
VulDB Temp Score: 2.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Prng seed
CWE: CWE-335 / CWE-331 / CWE-330
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: CryptX 0.088
Patch: 9a1dd3e0c27d68e32450be5538b864c2b115ee15

Timelineinfo

04/21/2026 CVE reserved
04/23/2026 +2 days Advisory disclosed
04/23/2026 +0 days VulDB entry created
04/23/2026 +0 days VulDB entry last update

Sourcesinfo

Advisory: GHSA-24c2-gp6c-24c6
Status: Confirmed

CVE: CVE-2026-41564 (🔒)
GCVE (CVE): GCVE-0-2026-41564
GCVE (VulDB): GCVE-100-359125
EUVD: 🔒

Entryinfo

Created: 04/23/2026 11:41
Updated: 04/23/2026 11:55
Changes: 04/23/2026 11:41 (60), 04/23/2026 11:55 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!