Unrated

Predictable PRNG output across forked processes in Bytes::Random::Secure

IdentifiersCVE-2026-11625CWE-335

CVE-2026-11625 affects Bytes::Random::Secure for Perl through version 0.29. The module can share pseudo-random number generator internal state across forked processes. The issue occurs when a Bytes::Random::Secure object is initialized before a fork, or when the module’s functional interface is used in a multiprocess context. Because the PRNG state is duplicated into child processes, multiple processes can emit identical random streams. As a result, secrets derived from this output in multiprocess applications may be predictable across processes.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

The vulnerability undermines the unpredictability of secrets generated by affected multiprocess Perl applications. If multiple forked processes produce identical or correlated random output, attackers may be able to predict generated secrets across processes, which can compromise tokens, nonces, session material, keys, or other security-sensitive values derived from the module. The primary impact is loss of cryptographic randomness guarantees rather than direct memory corruption or code execution.

Mitigation

If you can’t patch tonight, do this now.

Until a fixed release is deployed, avoid initializing Bytes::Random::Secure objects before forking. Do not use the functional interface in multiprocess contexts affected by forked state inheritance. If continued use is necessary, use only the object-oriented interface and instantiate the object separately in each child process after fork. The advisory also recommends considering alternative modules such as Crypt::PRNG, Crypt::SysRandom, or Crypt::URandom.

Remediation

Patch, then assume compromise.

Apply the published patch and upgrade Bytes::Random::Secure to a version newer than 0.29 once a fixed release is available. Review application code to ensure PRNG instances are not inherited across forks and validate that random state is independently initialized in each child process after forking.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

ACTIVITY FEED

Recent activity

6 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

6 SOURCESView more in app

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES

MITRE CVE

cve.org · CVE-2026-11625

NVD

nvd.nist.gov/vuln/detail/CVE-2026-11625

MITRE CWE · CWE-335

cwe.mitre.org