CVE-2026-11702

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
21.0%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 1, 2026

Advisory Details (4)

Auto-updated Jun 26, 2026
No patch confirmed yet. Sources: github_pr.
generic
https://www.cve.org/CVERecord?id=CVE-2026-41564
generic
https://security.metacpan.org/patches/B/Bytes-Random-Secure-Tiny/1.011/CVE-2026-11702-r1.patch
github_pr

Fix for CVE-2026-11702

Upstream fix in progress (PR #7 · daoswald/Bytes-Random-Secure-Tiny, state=open)

https://github.com/daoswald/Bytes-Random-Secure-Tiny/pull/7
generic

The internal PRNG state is not updated on forking · Issue #6 · daoswald/Bytes-Random-Secure-Tiny · GitHub

https://github.com/daoswald/Bytes-Random-Secure-Tiny/issues/6

Vendor Advisories for CVE-2026-11702(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 34× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 22:33 UTCEG score recompute
  2. 2026-07-06 22:33 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 09:28 UTCEG score recompute
  5. 2026-07-06 09:28 UTCGHSA enrichment
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 20:22 UTCEG score recompute
  8. 2026-07-05 20:22 UTCGHSA enrichment
  9. 2026-07-05 07:17 UTCEG score recompute
  10. 2026-07-05 07:16 UTCGHSA enrichment
  11. 2026-07-05 02:30 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 18:10 UTCEG score recompute
  14. 2026-07-04 18:10 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 05:01 UTCEG score recompute
  17. 2026-07-04 05:00 UTCGHSA enrichment
  18. 2026-07-03 15:53 UTCEG score recompute
  19. 2026-07-03 15:53 UTCGHSA enrichment
  20. 2026-07-03 02:47 UTCEG score recompute
  21. 2026-07-03 02:47 UTCGHSA enrichment
  22. 2026-07-02 13:41 UTCEG score recompute
  23. 2026-07-02 13:41 UTCGHSA enrichment
  24. 2026-07-02 00:36 UTCEG score recompute
  25. 2026-07-02 00:35 UTCGHSA enrichment
Show 21 more
  1. 2026-07-01 15:06 UTCEPSS rescore
  2. 2026-07-01 15:06 UTCEPSS rescore
  3. 2026-07-01 11:30 UTCEG score recompute
  4. 2026-07-01 11:30 UTCGHSA enrichment
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-30 22:23 UTCEG score recompute
  7. 2026-06-30 22:23 UTCGHSA enrichment
  8. 2026-06-30 09:18 UTCEG score recompute
  9. 2026-06-30 09:18 UTCGHSA enrichment
  10. 2026-06-29 20:13 UTCEG score recompute
  11. 2026-06-29 20:13 UTCGHSA enrichment
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 07:08 UTCEG score recompute▲ 7.50
  14. 2026-06-29 07:08 UTCGHSA enrichment
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-26 17:41 UTCNVD updateCVSS v3 → 7.5 · severity → HIGH
  20. 2026-06-26 09:38 UTCEG score recompute
  21. 2026-06-26 09:38 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-11702?
CVE-2026-11702 is a high vulnerability published on June 26, 2026. 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…
When was CVE-2026-11702 disclosed?
CVE-2026-11702 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11702 actively exploited?
CVE-2026-11702 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11702?
CVE-2026-11702 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-11702?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11702, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-11702

Explore →

Is Your Infrastructure Affected by CVE-2026-11702?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs