Skip to main content
CVE-2025-15578VulnerabilityPublished

CVE-2025-15578: TEEJAY Maypole · PRNG

Affects TEEJAY MaypoleSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Feb 2026

  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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
TEEJAYMaypoleAffected
  • >=2.10 <=2.13
Fixed in–

AI-suggested

Organizations should immediately assess their use of Maypole versions 2.10 through 2.13 and plan to upgrade to a version that addresses this vulnerability once released. In the absence of an official patch, developers should implement custom session ID generation using cryptographically secure PRNGs, such as those provided by the Crypt::PRNG or Crypt::Random Perl modules, ensuring high entropy and unpredictability. Additionally, session management should enforce strict expiration times and monitor for anomalous session activity to detect potential hijacking attempts. Web servers should be configured to minimize exposure of system time in HTTP headers to reduce information leakage. Employing multi-factor authentication can also mitigate the impact of session compromise. Regular security audits and penetration testing focused on session management will help identify and remediate weaknesses. Finally, organizations should stay informed about updates from TEEJAY and apply patches promptly upon release.

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.

References

Community reviews

Loading reviews…