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

> Attackers can recover private keys from preforking services due to shared PRNG state after forking in the CryptX Perl library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2026
- **Updated:** 23 Apr 2026
- **Also known as:** ALPINE-CVE-2026-41564, DEBIAN-CVE-2026-41564, GHSA-24c2-gp6c-24c6, UBUNTU-CVE-2026-41564, openSUSE-SU-2026:10773-1

## What is CVE-2026-41564?

CVE-2026-41564 is a high-severity vulnerability in MIK CryptX, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)), CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2026-41564?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-CryptX` | openSUSE:Tumbleweed | All versions | 0.89.0-1.1 |

Products: Dcit Cryptx.

## How do I fix CVE-2026-41564?

Upgrade to a fixed version.

## Is CVE-2026-41564 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41564 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41564 and fix it if it is affected.

What it is: CVE-2026-41564 is a high-severity vulnerability in MIK CryptX, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41564 exists.

Affected product: MIK CryptX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41564/ (Markdown: https://insights.sbomify.com/CVE-2026-41564/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41564
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41564
- OSV: https://osv.dev/vulnerability/CVE-2026-41564

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41564/
Summaries are generated and may contain mistakes; the official description above is the record.