How severe is CVE-2025-1860?

CVE-2025-1860 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2025-1860 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-1860?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-1860 have an EU (EUVD) identifier?

Yes. CVE-2025-1860 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-8533.

When was CVE-2025-1860 published?

CVE-2025-1860 was published on 2025-03-28 and last updated on 2026-06-17.

CVE-2025-1860

CVE-2025-1860 is a high-severity vulnerability with a CVSS 3.x base score of 7.7. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-331.

Key facts

Severity: High (CVSS 3.x base score 7.7)
EPSS exploit prediction: 0% (8th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-8533
Weakness: CWE-331
Published: 2025-03-28
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-1860?: 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.
How severe is CVE-2025-1860?: CVE-2025-1860 has a CVSS 3.x base score of 7.7, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2025-1860 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-1860?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-1860 have an EU (EUVD) identifier?: Yes. CVE-2025-1860 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-8533.
When was CVE-2025-1860 published?: CVE-2025-1860 was published on 2025-03-28 and last updated on 2026-06-17.

References

Other CWE-331 vulnerabilities

CVE-2020-36925 — Critical (CVSS 9.8): Arteco Web Client DVR/NVR contains a session hijacking vulnerability with insufficient session ID complexity that…
CVE-2025-47781 — Critical (CVSS 9.8): Rallly is an open-source scheduling and collaboration tool. Versions up to and including 3.22.1 of the application…
CVE-2024-47945 — Critical (CVSS 9.8): The devices are vulnerable to session hijacking due to insufficient entropy in its session ID generation algorithm.…
CVE-2024-25730 — Critical (CVSS 9.8): Hitron CODA-4582 and CODA-4589 devices have default PSKs that are generated from 5-digit hex values concatenated with a…
CVE-2023-49599 — Critical (CVSS 9.8): An insufficient entropy vulnerability exists in the salt generation functionality of WWBN AVideo dev master commit…
CVE-2022-34294 — Critical (CVSS 9.8): totd 1.5.3 uses a fixed UDP source port in upstream queries sent to DNS resolvers. This allows DNS cache poisoning…

Browse all CWE-331 vulnerabilities →