CVE-2025-15578

CVE-2025-15578 is a critical-severity vulnerability in Teejay Maypole with a CVSS 3.x base score of 9.8. 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-338.

Key facts

Description

Maypole versions from 2.10 through 2.13 for Perl generates session ids insecurely. The session id is seeded with the system time (which is available from HTTP response headers), a call to the built-in rand() function, and the PID.

Frequently asked questions

What is CVE-2025-15578?
Maypole versions from 2.10 through 2.13 for Perl generates session ids insecurely. The session id is seeded with the system time (which is available from HTTP response headers), a call to the built-in rand() function, and the PID.
How severe is CVE-2025-15578?
CVE-2025-15578 has a CVSS 3.x base score of 9.8, 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 high.
Is CVE-2025-15578 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-15578?
CVE-2025-15578 primarily affects Teejay Maypole. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-15578?
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-2025-15578 have an EU (EUVD) identifier?
Yes. CVE-2025-15578 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-207692.
When was CVE-2025-15578 published?
CVE-2025-15578 was published on 2026-02-16 and last updated on 2026-06-17.

References

Affected products (3)

Other CWE-338 vulnerabilities

Browse all CWE-338 vulnerabilities →