Unrated

Predictable random streams across forked processes in Bytes::Random::Secure::Tiny

IdentifiersCVE-2026-11702CWE-335

CVE-2026-11702 affects Bytes::Random::Secure::Tiny for Perl through version 1.011. The module's pseudo-random number generator state is inherited across forked processes when a Bytes::Random::Secure::Tiny object is initialized before a fork. As a result, parent and child processes can generate identical random streams from the shared internal PRNG state. In multiprocess applications, this can cause secrets derived from the affected generator to become 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.

An attacker who can observe or infer random output from one forked process may be able to predict secrets generated in another process using the same inherited PRNG state. This can undermine the security of tokens, nonces, session material, or other secrets generated by affected multiprocess Perl applications. The primary impact is loss of unpredictability of security-sensitive random values rather than direct memory corruption or code execution.

Mitigation

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

If patching is not immediately possible, do not initialize Bytes::Random::Secure::Tiny objects before calling fork(). Instead, instantiate a fresh random object separately in each child process after forking so that PRNG state is not shared. Where feasible, replace the module with alternatives recommended in the advisory, including Crypt::PRNG, Crypt::SysRandom, or Crypt::URandom.

Remediation

Patch, then assume compromise.

Upgrade to a version newer than 1.011 that fixes PRNG state sharing across forked processes. If an official patched release is available from the project or CPAN Security Group advisory, apply that update or patch. Validate that random generator instances are not reused across fork boundaries after remediation.

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-11702

NVD

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

MITRE CWE · CWE-335

cwe.mitre.org