Skip to main content
VulnerabilityPublished Updated

CVE-2026-8647: MIK Crypt::ScryptKDF · Use of Cryptographically Weak Pseudo-Random Number Generator

Affects MIK Crypt::ScryptKDFSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.8 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
MIKCrypt::ScryptKDFAffected
  • <=0.010
Fixed in–
GitHubCrypt-ScryptKDFpkg:github/Crypt-ScryptKDFOther threatsAffected
  • <=0.010
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should ensure that at least one supported CSPRNG Perl module (e.g., Crypt::PRNG, Crypt::OpenSSL::Random, Net::SSLeay, Crypt::Random, or Bytes::Random::Secure) is installed and available in their environment to avoid fallback to the insecure rand() function. Monitor the vendor advisory for updates regarding an official fix.

Description

CVE-2026-8647 is a medium severity vulnerability in the Perl module Crypt::ScryptKDF versions through 0.010. The module uses an insecure random number source when no cryptographically secure pseudo-random number generator (CSPRNG) module is available. Specifically, the random_bytes function falls back to the built-in rand() function, which is not cryptographically secure. This weakness can reduce the effectiveness of cryptographic operations relying on this module.

References

Community reviews

Loading reviews…