CVE-2025-15604: Amon2 versions before 6.17 for Perl use an insecure random_string implementation for security functions. In v
CVE-2025-15604 is a critical-severity flaw (CVSS 9.8) affecting amon2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Amon2 versions before 6.17 for Perl use an insecure random_string implementation for security functions. In versions 6.06 through 6.16, the random_string function will attempt to read bytes from the /dev/urandom device, but if that is unavailable then it generates bytes by concatenating a SHA-1 hash seeded with the built-in rand() function, the PID, and the high resolution epoch time. The PID will come from a small set of numbers, and the epoch
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-15604?
amon2: upgrade to 6.17. Exact commands for each OS are on this page.
Is CVE-2025-15604 being exploited?
CVE-2025-15604 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-15604 affect?
CVE-2025-15604 affects amon2. Severity is critical (CVSS 9.8). Amon2 versions before 6.17 for Perl use an insecure random_string implementation for security functions. In versions 6.06 through 6.16, the random_string function will attempt to read bytes from the /dev/urandom device, but if that is unav
How urgent is CVE-2025-15604?
Priority 50/100. Critical severity; Remotely exploitable, no login, no user action