When an object is initialised before forking, 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, if possible. Otherwise, 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::Tiny versions through 1.011 for Perl share internal state across forked processes. When an object is initialised before forking, 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::Tiny versions through 1.011 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:24:56.836Z
Reserved: 2026-06-08T22:09:13.472Z
Link: CVE-2026-11702
Updated: 2026-06-26T16:18:50.894Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-06-26T09:30:16Z