{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41564 exists.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-41564 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41564 exists.\n\nAffected product: MIK CryptX. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-41564/ (Markdown: https://insights.sbomify.com/CVE-2026-41564/index.md)","id":"CVE-2026-41564","markdown":"https://insights.sbomify.com/CVE-2026-41564/index.md","name":"CVE-2026-41564","record":{"aliases":["ALPINE-CVE-2026-41564","DEBIAN-CVE-2026-41564","GHSA-24c2-gp6c-24c6","UBUNTU-CVE-2026-41564","openSUSE-SU-2026:10773-1"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl CryptX library","requires_auth":"none","summary":"Attackers can recover private keys from preforking services due to shared PRNG state after forking in the CryptX Perl library.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CPANSec","cpe":[{"product":"cryptx","vendor":"dcit"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-338","name":"Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)"},{"id":"CWE-335","name":"Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)"}],"description":"CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking.\n\nThe 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.\n\nThis affects preforking services such as the Starman web server, where a Crypt::PK::* object loaded at startup is inherited by every worker process.","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"CryptX versions before 0.088 for Perl do not reseed the Crypt::PK PRNG state after forking","id":"CVE-2026-41564","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":1,"n_references":3,"next":{"headline":"CryptX versions before 0.088_001 for Perl have a stack buffer overflow in four AEAD decrypt_verify helpers","id":"CVE-2026-41565"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["0.89.0-1.1"],"introduced":["0"],"last_affected":[],"package":"perl-CryptX","purl":"pkg:rpm/opensuse/perl-CryptX\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:10773-1"}],"prev":{"headline":"WordPress Sitemovr plugin \u003c= 1.0.1 - Sensitive Data Exposure vulnerability","id":"CVE-2026-41563"},"products":["CryptX"],"published":"2026-04-23","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-23","vendors":["MIK"]},"summary":"Attackers can recover private keys from preforking services due to shared PRNG state after forking in the CryptX Perl library.","url":"https://insights.sbomify.com/CVE-2026-41564/"}