CVE-2026-11625

CVE-2026-11625 is a high-severity vulnerability with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-335.

Key facts

Description

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.

Frequently asked questions

What is CVE-2026-11625?
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.
How severe is CVE-2026-11625?
CVE-2026-11625 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-11625 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (23rd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-11625?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-11625 have an EU (EUVD) identifier?
Yes. CVE-2026-11625 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-39640.
When was CVE-2026-11625 published?
CVE-2026-11625 was published on 2026-06-26 and last updated on 2026-07-01.

References

Other CWE-335 vulnerabilities

Browse all CWE-335 vulnerabilities →