CVSS 3.1
9.0 criticalCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:HCritical (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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:Hcrypto-js (npm): fixed in 4.0.0Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| brix crypto-js | < 4.0.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-rg76-677x-56q9 | npm | crypto-js | <4.0.0 | 4.0.0 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | cryptojs | no fix listed | DEBIAN-CVE-2026-71851 |
| Ubuntu | 20.04:LTS, 24.04:LTS, Pro:16.04:LTS and 2 more | cryptojs | no fix listed | UBUNTU-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 rates this Important.
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.
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).
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat build of Apache Camel for Spring Boot 4 | rhaf-camel-for-springboot-maven-repository.zip | Not affected | |
| Red Hat build of Apache Camel for Spring Boot 4 | rhaf-camel-spring-boot-maven-repository.zip | Not affected | |
| Red Hat Enterprise Linux 10 | dotnet8.0 | Not affected | |
| Red Hat Enterprise Linux 10 | dotnet9.0 | Not affected | |
| Red Hat Enterprise Linux 8 | dotnet8.0 | Not affected | |
| Red Hat Enterprise Linux 8 | dotnet9.0 | Not affected | |
| Red Hat Enterprise Linux 9 | dotnet8.0 | Not affected | |
| Red Hat Enterprise Linux 9 | dotnet9.0 | Not affected | |
| Red Hat Hardened Images | dotnet10.0 | Not affected | |
| Red Hat Hardened Images | dotnet8.0 | Not affected | |
| Red Hat Hardened Images | dotnet9.0 | Not affected | |
| Red Hat Satellite 6 | satellite/iop-advisor-frontend-rhel9 | Not 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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.