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.5% (44th percentile of EPSS-scored CVEs). 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.5%CVSS: 9.0Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.0CRITICALmedium confidence
EG Risk
57
EG Risk 57/100CISA SSVC

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%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 7, 2026

Last Modified

September 9, 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 rangeFix by version rangeDependents
cryptojs3.1.2+dfsg-3, 3.1.2+dfsg-4
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
cryptojs3.1.2+dfsg-3, 3.1.2+dfsg-4
  • every version on: no fix on record
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
crypto-js—
  • every version up to 4.0.0: fixed in 4.0.0
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 11× 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.

Showing the most recent 100 of 104 total refreshes for this CVE.

  1. 2026-10-05 08:13 UTCEG score recompute
  2. 2026-10-04 23:22 UTCEPSS rescore
  3. 2026-10-04 05:42 UTCEG score recompute
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 00:59 UTCEG score recompute
  6. 2026-10-02 09:32 UTCEG score recompute
  7. 2026-10-01 19:50 UTCEPSS rescore
  8. 2026-09-30 22:54 UTCEG score recompute
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-29 05:45 UTCEG score recompute
  11. 2026-09-28 13:52 UTCEPSS rescore
  12. 2026-09-27 17:08 UTCEG score recompute
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:59 UTCEPSS rescore
  15. 2026-09-25 04:15 UTCEG score recompute
  16. 2026-09-23 21:16 UTCEG score recompute
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-22 21:19 UTCEG score recompute
  19. 2026-09-22 00:42 UTCEG score recompute
  20. 2026-09-21 21:09 UTCEPSS rescore
  21. 2026-09-20 20:32 UTCEG score recompute
  22. 2026-09-20 20:16 UTCEPSS rescore
  23. 2026-09-19 17:29 UTCEG score recompute
  24. 2026-09-18 22:16 UTCEG score recompute
  25. 2026-09-18 19:28 UTCEPSS rescore
Show 75 more
  1. 2026-09-18 00:55 UTCEG score recompute
  2. 2026-09-17 00:53 UTCEG score recompute
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 06:37 UTCEG score recompute
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 06:34 UTCEG score recompute
  7. 2026-09-15 03:12 UTCEPSS rescore
  8. 2026-09-13 19:48 UTCEG score recompute
  9. 2026-09-12 17:01 UTCEG score recompute
  10. 2026-09-12 15:02 UTCEPSS rescore
  11. 2026-09-11 18:13 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescore
  13. 2026-09-11 14:26 UTCEG score recompute
  14. 2026-09-10 10:15 UTCEG score recompute
  15. 2026-09-10 09:35 UTCEPSS rescore
  16. 2026-09-09 06:00 UTCEG score recompute
  17. 2026-09-08 22:01 UTCEPSS rescore
  18. 2026-09-07 17:43 UTCEG score recompute
  19. 2026-09-06 14:55 UTCEG score recompute
  20. 2026-09-06 13:48 UTCEPSS rescore
  21. 2026-09-05 16:10 UTCEG score recompute
  22. 2026-09-04 16:47 UTCEG score recompute
  23. 2026-09-04 09:02 UTCEG score recompute
  24. 2026-09-04 05:07 UTCEPSS rescore
  25. 2026-09-03 05:59 UTCEG score recompute
  26. 2026-09-02 14:12 UTCEPSS rescore
  27. 2026-09-01 17:38 UTCEG score recompute
  28. 2026-09-01 13:54 UTCEPSS rescore
  29. 2026-09-01 07:10 UTCEG score recompute
  30. 2026-09-01 04:40 UTCEPSS rescore
  31. 2026-08-30 19:46 UTCEG score recompute
  32. 2026-08-30 19:17 UTCEPSS rescore
  33. 2026-08-30 04:38 UTCEG score recompute
  34. 2026-08-30 01:22 UTCEPSS rescore
  35. 2026-08-29 10:22 UTCEG score recompute
  36. 2026-08-28 21:42 UTCEPSS rescore
  37. 2026-08-27 19:48 UTCEG score recompute
  38. 2026-08-26 16:32 UTCEG score recompute
  39. 2026-08-26 14:47 UTCEPSS rescore
  40. 2026-08-25 16:31 UTCEG score recompute
  41. 2026-08-25 13:49 UTCEPSS rescore
  42. 2026-08-24 17:33 UTCEG score recompute
  43. 2026-08-24 09:58 UTCEG score recompute
  44. 2026-08-23 03:08 UTCEG score recompute
  45. 2026-08-23 00:19 UTCEPSS rescore
  46. 2026-08-22 00:25 UTCEG score recompute
  47. 2026-08-21 23:49 UTCEPSS rescore
  48. 2026-08-21 01:37 UTCEG score recompute
  49. 2026-08-20 22:56 UTCEPSS rescore
  50. 2026-08-19 18:47 UTCEG score recompute
  51. 2026-08-19 17:04 UTCEPSS rescore
  52. 2026-08-18 15:39 UTCEG score recompute
  53. 2026-08-18 13:49 UTCEPSS rescore
  54. 2026-08-18 13:49 UTCEPSS rescore
  55. 2026-08-17 15:33 UTCEG score recompute
  56. 2026-08-17 13:47 UTCEPSS rescore
  57. 2026-08-16 16:52 UTCEG score recompute
  58. 2026-08-16 14:56 UTCEPSS rescore
  59. 2026-08-16 14:56 UTCEPSS rescore
  60. 2026-08-16 05:33 UTCEG score recompute
  61. 2026-08-16 02:15 UTCEPSS rescore
  62. 2026-08-15 02:40 UTCEG score recompute
  63. 2026-08-15 01:31 UTCEPSS rescore
  64. 2026-08-14 00:14 UTCEG score recompute
  65. 2026-08-13 22:00 UTCEPSS rescore
  66. 2026-08-12 14:10 UTCEG score recompute
  67. 2026-08-12 13:51 UTCEPSS rescore
  68. 2026-08-11 15:30 UTCEG score recompute
  69. 2026-08-11 00:23 UTCEG score recompute
  70. 2026-08-11 00:00 UTCEPSS rescore
  71. 2026-08-09 14:24 UTCEG score recompute
  72. 2026-08-09 13:47 UTCEPSS rescore
  73. 2026-08-08 19:31 UTCEG score recompute
  74. 2026-08-08 16:37 UTCEPSS rescore
  75. 2026-08-08 04:24 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

2 shown

Debian:11:cryptojs

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 on August 7, 2026, with the most recent update on September 9, 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.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71851?
CVE-2026-71851 has a CVSS base score of 9.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71851?
A fix for CVE-2026-71851 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71851 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs