# CVE-2025-1860: Data::Entropy for Perl uses insecure rand() function for cryptographic functions

> The Data::Entropy Perl library uses insecure random number generation for cryptographic functions, potentially compromising security.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Mar 2025
- **Updated:** 5 Sep 2025
- **Also known as:** DEBIAN-CVE-2025-1860, DLA-4100-1, GHSA-g3hm-j3wc-jcg9, MGASA-2025-0279, UBUNTU-CVE-2025-1860, openSUSE-SU-2025:0123-1, openSUSE-SU-2025:14960-1

## What is CVE-2025-1860?

CVE-2025-1860 is a high-severity vulnerability in ZEFRAM Data::Entropy, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Data::Entropy for Perl 0.007 and earlier use the rand() function as the default source of entropy, which is not cryptographically secure, for cryptographic functions.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)), CWE-331 (Insufficient Entropy)

## Which versions are affected by CVE-2025-1860?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-Data-Entropy` | SUSE:Package Hub 15 SP6 | All versions | 0.8.0-bp156.4.3.1 |
| `perl-Data-Entropy` | openSUSE:Leap 15.6 | All versions | 0.8.0-bp156.4.3.1 |
| `perl-Data-Entropy` | openSUSE:Tumbleweed | All versions | 0.8.0-1.1 |

## How do I fix CVE-2025-1860?

Upgrade to a fixed version.

## Is CVE-2025-1860 being exploited?

There is no known exploitation of CVE-2025-1860 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1860 and fix it if it is affected.

What it is: CVE-2025-1860 is a high-severity vulnerability in ZEFRAM Data::Entropy, published on 28 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1860 in the wild and no public exploit code.

Affected product: ZEFRAM Data::Entropy. 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-2025-1860/ (Markdown: https://insights.sbomify.com/CVE-2025-1860/index.md)
```

## Sources

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

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