Skip to content
Fencer Vulns
high 7.5

CVE-2026-11625 json

Bytes::Random::Secure versions through 0.29 for Perl share internal state across forked processes

published 2026-06-26 4 mo ago modified 2026-10-25 14 d ago also EUVD-2026-39640

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits
0
none known

Summary

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.

Patch / fix

  • libbytes-random-secure-perl Debian 12 0.29-4~deb13u1~deb12u1
  • libbytes-random-secure-perl Debian 13 0.29-4~deb13u1
  • libbytes-random-secure-perl Debian 14 0.29-4

debian advisories DEBIAN-CVE-2026-11625

  • perl-Bytes-Random-Secure Azure Linux 3.0 0.29-22

azure linux advisories AZL-91571

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

  • DAVIDO Bytes::Random::Secure

Classification

Weakness
  • CWE-335 Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.