CVE-2026-11625

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/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
Severity75% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 1, 2026

Advisory Details (4)

Auto-updated Jun 26, 2026
No patch confirmed yet. Sources: github_pr.
generic
https://www.cve.org/CVERecord?id=CVE-2026-41564
generic
https://security.metacpan.org/patches/B/Bytes-Random-Secure/0.29/CVE-2026-11625-r1.patch
github_pr

Fix for CVE-2026-11625

Upstream fix in progress (PR #4 · daoswald/Bytes-Random-Secure, state=open)

https://github.com/daoswald/Bytes-Random-Secure/pull/4
generic

The internal PRNG state is not updated on forking · Issue #3 · daoswald/Bytes-Random-Secure · GitHub

https://github.com/daoswald/Bytes-Random-Secure/issues/3

Vendor Advisories for CVE-2026-11625(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 98× 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.

Showing the most recent 100 of 102 total refreshes for this CVE.

  1. 2026-07-27 03:41 UTCEG score recompute
  2. 2026-07-27 03:41 UTCVendor advisory
  3. 2026-07-27 03:41 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:43 UTCEG score recompute
  7. 2026-07-26 14:43 UTCVendor advisory
  8. 2026-07-26 14:43 UTCGHSA enrichment
  9. 2026-07-25 14:17 UTCEPSS rescore
  10. 2026-07-24 14:17 UTCEPSS rescore
  11. 2026-07-23 14:18 UTCEPSS rescore
  12. 2026-07-23 03:04 UTCEG score recompute
  13. 2026-07-22 14:08 UTCEPSS rescore
  14. 2026-07-21 15:24 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 02:28 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-17 04:57 UTCVendor advisory
  19. 2026-07-17 04:57 UTCGHSA enrichment
  20. 2026-07-16 17:02 UTCEPSS rescore
  21. 2026-07-16 16:20 UTCGHSA enrichment
  22. 2026-07-16 03:39 UTCVendor advisory
  23. 2026-07-16 03:39 UTCGHSA enrichment
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 15:02 UTCVendor advisory
Show 75 more
  1. 2026-07-15 15:02 UTCGHSA enrichment
  2. 2026-07-15 02:26 UTCVendor advisory
  3. 2026-07-15 02:26 UTCGHSA enrichment
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-14 13:50 UTCVendor advisory
  6. 2026-07-14 13:50 UTCGHSA enrichment
  7. 2026-07-14 01:14 UTCVendor advisory
  8. 2026-07-14 01:14 UTCGHSA enrichment
  9. 2026-07-13 22:30 UTCEPSS rescore
  10. 2026-07-13 12:38 UTCGHSA enrichment
  11. 2026-07-13 06:12 UTCEPSS rescore
  12. 2026-07-13 00:02 UTCVendor advisory
  13. 2026-07-13 00:02 UTCGHSA enrichment
  14. 2026-07-12 11:24 UTCVendor advisory
  15. 2026-07-12 11:24 UTCGHSA enrichment
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 22:48 UTCVendor advisory
  18. 2026-07-11 22:48 UTCGHSA enrichment
  19. 2026-07-11 10:12 UTCVendor advisory
  20. 2026-07-11 10:12 UTCGHSA enrichment
  21. 2026-07-11 08:27 UTCEPSS rescore
  22. 2026-07-10 21:36 UTCVendor advisory
  23. 2026-07-10 21:36 UTCGHSA enrichment
  24. 2026-07-10 09:00 UTCVendor advisory
  25. 2026-07-10 09:00 UTCGHSA enrichment
  26. 2026-07-09 20:25 UTCVendor advisory
  27. 2026-07-09 20:25 UTCGHSA enrichment
  28. 2026-07-09 19:10 UTCEPSS rescore
  29. 2026-07-09 07:48 UTCVendor advisory
  30. 2026-07-09 07:48 UTCGHSA enrichment
  31. 2026-07-08 19:12 UTCVendor advisory
  32. 2026-07-08 19:11 UTCGHSA enrichment
  33. 2026-07-08 15:15 UTCEPSS rescore
  34. 2026-07-08 15:15 UTCEPSS rescore
  35. 2026-07-08 06:34 UTCVendor advisory
  36. 2026-07-08 06:34 UTCGHSA enrichment
  37. 2026-07-07 17:58 UTCVendor advisory
  38. 2026-07-07 17:58 UTCGHSA enrichment
  39. 2026-07-07 13:46 UTCEPSS rescore
  40. 2026-07-07 05:21 UTCVendor advisory
  41. 2026-07-07 05:21 UTCGHSA enrichment
  42. 2026-07-06 16:43 UTCVendor advisory
  43. 2026-07-06 16:43 UTCGHSA enrichment
  44. 2026-07-06 16:27 UTCEPSS rescore
  45. 2026-07-06 04:06 UTCVendor advisory
  46. 2026-07-06 04:06 UTCGHSA enrichment
  47. 2026-07-06 02:23 UTCEPSS rescore
  48. 2026-07-05 15:29 UTCVendor advisory
  49. 2026-07-05 15:29 UTCGHSA enrichment
  50. 2026-07-05 02:49 UTCVendor advisory
  51. 2026-07-05 02:49 UTCGHSA enrichment
  52. 2026-07-05 02:30 UTCEPSS rescore
  53. 2026-07-05 02:30 UTCEPSS rescore
  54. 2026-07-04 14:13 UTCVendor advisory
  55. 2026-07-04 14:13 UTCGHSA enrichment
  56. 2026-07-04 01:37 UTCGHSA enrichment
  57. 2026-07-03 12:59 UTCGHSA enrichment
  58. 2026-07-03 00:24 UTCGHSA enrichment
  59. 2026-07-02 11:48 UTCGHSA enrichment
  60. 2026-07-01 23:11 UTCGHSA enrichment
  61. 2026-07-01 15:06 UTCEPSS rescore
  62. 2026-07-01 15:06 UTCEPSS rescore
  63. 2026-07-01 10:34 UTCGHSA enrichment
  64. 2026-06-30 23:22 UTCEPSS rescore
  65. 2026-06-30 21:58 UTCGHSA enrichment
  66. 2026-06-30 09:22 UTCGHSA enrichment
  67. 2026-06-29 20:46 UTCGHSA enrichment
  68. 2026-06-29 14:06 UTCEPSS rescore
  69. 2026-06-29 08:08 UTCEG score recompute▲ 7.50
  70. 2026-06-29 08:08 UTCGHSA enrichment
  71. 2026-06-28 14:07 UTCEPSS rescore
  72. 2026-06-28 04:56 UTCEPSS rescore
  73. 2026-06-28 04:56 UTCEPSS rescore
  74. 2026-06-27 03:08 UTCEPSS rescore
  75. 2026-06-26 17:41 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH

Frequently asked(5)

What is CVE-2026-11625?
CVE-2026-11625 is a high vulnerability published on June 26, 2026. 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.…
When was CVE-2026-11625 disclosed?
CVE-2026-11625 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11625 actively exploited?
CVE-2026-11625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.6% of all scored CVEs.
What is the CVSS score of CVE-2026-11625?
CVE-2026-11625 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-11625?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11625, 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-2026-11625

Explore →

Is Your Infrastructure Affected by CVE-2026-11625?

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

Start Free Scan →Browse All CVEs