Secret prediction via forked PRNG state reuse
Published Jun 26, 2026 · Updated Jun 26, 2026
Predictable randomness in Bytes::Random::Secure 0 through 0.29 allows attackers to infer secrets generated by forked Perl processes. The bytes, _ranged_randoms, and irand paths reuse an inherited Math::Random::ISAAC instance because they do not compare the current PID with the PID that seeded it. Exposure requires a process to initialize the object before fork, or use the functional interface, causing parent and child processes to emit identical streams.
Summary
What happened
Predictable randomness in Bytes::Random::Secure 0 through 0.29 allows attackers to infer secrets generated by forked Perl processes. The bytes, _ranged_randoms, and irand paths reuse an inherited Math::Random::ISAAC instance because they do not compare the current PID with the PID that seeded it. Exposure requires a process to initialize the object before fork, or use the functional interface, causing parent and child processes to emit identical streams.
The record
- CVE
- CVE-2026-11625
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- David J. Oswald
- Product
- Bytes::Random::Secure
- Classifications
- CWE-335
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.29
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo