Skip to main content
VulnerabilityPublished Updated

CVE-2025-1828: perl Crypt::Random · PRNG

Affects perl Crypt::RandomSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
perl Crypt::RandomAffected
  • =1.05
Fixed in–

AI-suggested

European organizations should take immediate steps to mitigate this vulnerability beyond generic patching advice. First, audit all Perl applications and scripts to identify usage of the Crypt::Random module, especially on Windows platforms. Explicitly configure Crypt::Random to use secure entropy sources such as /dev/urandom or an Entropy Gathering Daemon (egd) where available. For Windows systems, consider deploying or configuring a secure entropy provider compatible with Crypt::Random or switch to alternative cryptographic libraries that do not rely on weak PRNGs. Implement strict code review policies to ensure no fallback to insecure PRNGs occurs. Additionally, monitor cryptographic key generation processes for anomalies and consider reissuing keys or tokens generated during the vulnerable period. Organizations should also educate developers about the risks of using non-cryptographically secure random functions in security-sensitive contexts. Finally, maintain up-to-date Perl environments and apply patches as soon as they become available from the vendor or community.

Description

Crypt::Random Perl package 1.05 through 1.55 may use rand() function, which is not cryptographically strong, for cryptographic functions. If the Provider is not specified and /dev/urandom or an Entropy Gathering Daemon (egd) service is not available Crypt::Random will default to use the insecure Crypt::Random::rand provider. In particular, Windows versions of perl will encounter this issue by default.

References

Community reviews

Loading reviews…