CVE-2026-71851

CRITICALPre-NVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.0Exploit: Elevated riskExposed: 0

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

crypto-js is a JavaScript library of crypto standards. Versions of crypto-js prior to 4.0.0 generate randomness in CryptoJS.lib.WordArray.random() using a custom variation of the Multiply-With-Carry pseudorandom number generator, seeded from Math.random(), instead of a cryptographically secure source. This generator was introduced in version 3.1.2-4 and remained present in nearly every 3.x release. Nominal requests for 128 or 256 bits of entropy through this function produce effective search spaces of approximately 2 to the 39th and 2 to the 47th possibilities, small enough to enumerate on commodity hardware. Downstream wallet applications that used CryptoJS.lib.WordArray.random() as the entropy source for BIP39 recovery phrases are affected, and an attacker who enumerates the reduced output space can recover the resulting private keys and control the associated funds. This issue is fixed in version 4.0.0.

CVSS v3
9.0
EG Score
9.0(medium)
EG Risk
57(Track*)
EG Risk 57/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 8, 2026

Advisory Details (3)

Auto-updated Aug 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

Ill Bloom: Investigating a Wallet Generation Vulnerability During Active Exploitation

https://www.coinspect.com/blog/ill-bloom-investigation
github Patch Available🟡 PoC Available

CryptoJS.lib.WordArray.random() uses a weak PRNG (Ill Bloom) · Advisory · brix/crypto-js · GitHub

https://github.com/brix/crypto-js/security/advisories/GHSA-rg76-677x-56q9
github_commit

commit b405ff597fb3 (brix/crypto-js)

Fix landed in brix/crypto-js commit b405ff597fb3 — awaiting tagged release

https://github.com/brix/crypto-js/commit/b405ff597fb3ac76a7bdfbc72dca10ba1079b1d5

Vendor Advisories for CVE-2026-71851(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
cryptojs3.1.2+dfsg-3, 3.1.2+dfsg-4——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
cryptojs3.1.2+dfsg-3, 3.1.2+dfsg-4——
npm(1)
PackageVulnerable rangeFixed inDependents
crypto-js—4.0.0—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 32× 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-08-21 01:37 UTCEG score recompute
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-19 18:47 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 15:39 UTCEG score recompute
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-17 15:33 UTCEG score recompute
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 16:52 UTCEG score recompute
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 05:33 UTCEG score recompute
  14. 2026-08-16 02:15 UTCEPSS rescore
  15. 2026-08-15 02:40 UTCEG score recompute
  16. 2026-08-15 01:31 UTCEPSS rescore
  17. 2026-08-14 00:14 UTCEG score recompute
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 14:10 UTCEG score recompute
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-11 15:30 UTCEG score recompute
  22. 2026-08-11 00:23 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 14:24 UTCEG score recompute
  25. 2026-08-09 13:47 UTCEPSS rescore
Show 7 more
  1. 2026-08-08 19:31 UTCEG score recompute
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-08 04:24 UTCEG score recompute
  4. 2026-08-08 03:27 UTCEG score recompute
  5. 2026-08-07 19:28 UTCEG score recompute
  6. 2026-08-07 19:12 UTCEG score recompute
  7. 2026-08-07 19:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-71851?
CVE-2026-71851 is a critical vulnerability published on August 7, 2026. crypto-js is a JavaScript library of crypto standards. Versions of crypto-js prior to 4.0.0 generate randomness in CryptoJS.lib.WordArray.random() using a custom variation of the Multiply-With-Carry pseudorandom number generator, seeded from Math.random(), instead of a cryptographically secure…
When was CVE-2026-71851 disclosed?
CVE-2026-71851 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on August 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-71851 actively exploited?
CVE-2026-71851 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.4% of all scored CVEs.
What is the CVSS score of CVE-2026-71851?
CVE-2026-71851 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-71851?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-71851, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-71851

Explore →

Is Your Infrastructure Affected by CVE-2026-71851?

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

Start Free Scan →Browse All CVEs