CVE-2026-11625

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

Published Jun 26, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Bytes::Random::Secure versions through 0.29 for Perl store the internal state of the pseudorandom number generator in a process‑wide global. When an object is created before a fork, or when the functional API is used, that state is duplicated in child processes, causing each process to generate the same sequence of random numbers. Secrets produced in a multiprocess application are therefore identical and predictable, creating a risk that attackers can anticipate or replay secret values.

Affected Systems

The vulnerability affects the DAVIDO Bytes::Random::Secure CPAN module, versions 0.29 and earlier. Applications that import this module and use it in a forked environment are impacted.

Risk and Exploitability

The likely attack vector is an application that uses Bytes::Random::Secure before forking and relies on the generated values for cryptographic or authentication purposes. Based on the description, it is inferred that an attacker who can influence or observe a forked process may predict deterministic secrets. EPSS score is <1% and the vulnerability is not listed in the CISA KEV catalog, the raw risk level is unclear, but the nature of the flaw is serious. The CVSS score is 7.5, and the consequences could allow exploitation of predictable secrets.

Remediation

Vendor Workaround

Apply the patch. Otherwise, only use the object-oriented interface and ensure that the object is only instantiated in a child process after forking. Alternatively, use a different module such as Crypt::PRNG, Crypt::SysRandom or Crypt::URandom.


OpenCVE Recommended Actions

  • Apply the vendor patch (CVE-2026-11625-r1.patch) to all installed copies of Bytes::Random::Secure early versions.
  • Reinitialize the Bytes::Random::Secure object after a fork, ensuring that each child process creates its own PRNG instance.
  • Switch to a different random number module, such as Crypt::PRNG, Crypt::SysRandom, or Crypt::URandom, which do not share state across processes.

Generated by OpenCVE AI on June 26, 2026 at 18:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Davido
Davido bytes::random::secure
Vendors & Products Davido
Davido bytes::random::secure
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Bytes::Random::Secure versions through 0.29 for Perl share internal state across forked processes
Weaknesses CWE-335
References
Weaknesses
  • CWE-335

    Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)

Sources

Status
PUBLISHED
Assigner
CPANSec
Published
Updated
Jul 1, 2026, 2:34 PM
Reserved
Jun 8, 2026, 9:02 PM
Status
Deferred
Published
Jun 26, 2026, 9:16 AM
Modified
Oct 25, 2026, 10:10 PM