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.
Project Subscriptions
No data.
No advisories yet.
Solution
No solution given by the 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.
Fri, 26 Jun 2026 17:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Fri, 26 Jun 2026 08:45:00 +0000
| 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 |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: CPANSec
Published:
Updated: 2026-06-26T16:14:22.833Z
Reserved: 2026-06-08T21:02:09.596Z
Link: CVE-2026-11625
Updated: 2026-06-26T16:14:06.949Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-26T18:30:05Z