How severe is CVE-2024-58040?

CVE-2024-58040 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2024-58040 being actively exploited?

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

What products are affected by CVE-2024-58040?

CVE-2024-58040 affects Qwer Crypt. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2024-58040?

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

Does CVE-2024-58040 have an EU (EUVD) identifier?

Yes. CVE-2024-58040 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-55029.

When was CVE-2024-58040 published?

CVE-2024-58040 was published on 2025-09-30 and last updated on 2026-06-17.

CVE-2024-58040

CVE-2024-58040 is a critical-severity vulnerability in Qwer Crypt with a CVSS 3.x base score of 9.1. 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: Critical (CVSS 3.x base score 9.1)
EPSS exploit prediction: 0% (13th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2024-55029
Weakness: CWE-331
Affected product: Qwer Crypt
Published: 2025-09-30
Last modified: 2026-06-17

Description

Crypt::RandomEncryption for Perl version 0.01 uses insecure rand() function during encryption.

Frequently asked questions

What is CVE-2024-58040?: Crypt::RandomEncryption for Perl version 0.01 uses insecure rand() function during encryption.
How severe is CVE-2024-58040?: CVE-2024-58040 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2024-58040 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (13th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-58040?: CVE-2024-58040 affects Qwer Crypt. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-58040?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2024-58040 have an EU (EUVD) identifier?: Yes. CVE-2024-58040 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-55029.
When was CVE-2024-58040 published?: CVE-2024-58040 was published on 2025-09-30 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:qwer:crypt\:\:randomencryption:0.01:*:*:*:*:perl:*:*

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 →