cve.bz

CVE-2026-71851 brix crypto-js: Insufficient Entropy

9.0 criticalEPSS 0.5%Fix available

Critical (9.0) in brix crypto-js. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in crypto-js 4.0.0.

On this page
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.

Severity

CVSS 3.1

9.0 critical
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-08-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-331 Insufficient Entropy
CWE-334 Small Space of Random Values
CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
OWASP Top 10
A04:2025 Cryptographic Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • crypto-js (npm): fixed in 4.0.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-71851 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71851?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71851?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71851 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
brix crypto-js< 4.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rg76-677x-56q9npmcrypto-js<4.0.04.0.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12cryptojsno fix listedDEBIAN-CVE-2026-71851
Ubuntu20.04:LTS, 24.04:LTS, Pro:16.04:LTS and 2 morecryptojsno fix listedUBUNTU-CVE-2026-71851

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Impact has been assessed as Important. Exploitation requires a consuming application to specifically call CryptoJS.lib.WordArray.random() to generate security-sensitive values (for example, cryptocurrency wallet recovery phrases); merely depending on a vulnerable crypto-js release is not sufficient to be exploitable.

Successful exploitation additionally requires brute-force enumeration of a reduced, but non-trivial, entropy search space rather than a straightforward unauthenticated network attack.

Red Hat products bundling crypto-js (as an npm dependency of the .NET SDK, the Vaultwarden web client, Cockatrice, Insights Chrome, Camel Spring Boot, and the Satellite Insights Advisor frontend) already ship crypto-js 4.2.0, which includes the upstream fix, and are not known to use CryptoJS.lib.WordArray.random() to generate security-sensitive values such as cryptographic keys or wallet recovery phrases.

Red Hat's mitigation

There is no mitigation for this issue other than upgrading to crypto-js 4.0.0 or later, which replaces the affected pseudo-random number generator with the platform's native cryptographic API (Web Crypto API / Node.js crypto module).

ProductPackageStateAdvisory
Red Hat build of Apache Camel for Spring Boot 4rhaf-camel-for-springboot-maven-repository.zipNot affected
Red Hat build of Apache Camel for Spring Boot 4rhaf-camel-spring-boot-maven-repository.zipNot affected
Red Hat Enterprise Linux 10dotnet8.0Not affected
Red Hat Enterprise Linux 10dotnet9.0Not affected
Red Hat Enterprise Linux 8dotnet8.0Not affected
Red Hat Enterprise Linux 8dotnet9.0Not affected
Red Hat Enterprise Linux 9dotnet8.0Not affected
Red Hat Enterprise Linux 9dotnet9.0Not affected
Red Hat Hardened Imagesdotnet10.0Not affected
Red Hat Hardened Imagesdotnet8.0Not affected
Red Hat Hardened Imagesdotnet9.0Not affected
Red Hat Satellite 6satellite/iop-advisor-frontend-rhel9Not affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-71851.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • brendonlee20042004-sys/weakrng-sweep Harbor Check: matches CVE 0 stars, created
    Weak-RNG stream-sweep research (CVE-2026-71851 class): PRNG schemes x seeds -> BIP39 -> victim set membership

Attack patterns (CAPEC)

  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON