Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
A fix is available — apply it.
Bytes::Random::Secure versions through 0.29 for Perl share internal state across forked processes.
When an object is initialised before forking, or when the functional interface is used, then the internal state for the PRNG is shared across processes and identical random streams will be produced.
Secrets generated in multiprocess applications are predictable across processes.
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).
June 26, 2026
July 1, 2026
Upstream fix in progress (PR #4 · daoswald/Bytes-Random-Secure, state=open)
https://github.com/daoswald/Bytes-Random-Secure/pull/4These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Bytes::Random::Secure versions through 0.29 for Perl share internal state across forked processes
Bytes::Random::Secure versions through 0.29 for Perl share internal state across forked processes...
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libbytes-random-secure-perl | 0.29-1 ... 0.29-4~deb13u1~deb12u1 (6 versions) |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libbytes-random-secure-perl | 0.29-3 |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libbytes-random-secure-perl | 0.29-3, 0.29-4~deb13u1~deb12u1 |
| — |
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| libbytes-random-secure-perl | 0.29-3, 0.29-4~deb13u1, 0.29-4~deb13u1~deb12u1 |
| — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
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.
Showing the most recent 100 of 302 total refreshes for this CVE.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11625
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.