CVE-2025-15604

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-28. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage.

Before version 6.06, there was no fallback when /dev/urandom was not available.

Before version 6.04, the random_string function used the built-in rand() function to generate a mixed-case alphanumeric string.

This function may be used for generating session ids, generating secrets for signing or encrypting cookie session data and generating tokens used for Cross Site Request Forgery (CSRF) protection.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
EPSS %ILE
KEV
Not listed

Published

March 28, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Jul 27, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

oss-security - CVE-2025-15604: Amon2 versions before 6.17 for Perl use an insecure random_string implementation for security functions

http://www.openwall.com/lists/oss-security/2026/03/28/4
generic

CPAN Author’s Guide to Random Data for Security — CPAN Security Group (CPANSec) 🦆

https://security.metacpan.org/docs/guides/random-data-for-security.html
github_pr

Replace random_string with Crypt::SysRandom

Fix merged in tokuhirom/Amon PR #135 on 2026-02-27 — awaiting tagged release

https://github.com/tokuhirom/Amon/pull/135

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 2× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:19 UTCEG score recompute
  2. 2026-07-27 14:18 UTCGHSA enrichment

Frequently asked(4)

What is CVE-2025-15604?
CVE-2025-15604 is a critical vulnerability published on March 28, 2026. 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…
When was CVE-2025-15604 disclosed?
CVE-2025-15604 was first published in the National Vulnerability Database on March 28, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2025-15604?
CVE-2025-15604 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2025-15604?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-15604, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-15604

Explore →

Is Your Infrastructure Affected by CVE-2025-15604?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.