Secret recovery via weak pseudorandom generation
Published Aug 7, 2026 · Updated Aug 7, 2026
Insufficient entropy in Brix crypto-js before 4.0.0 allows attackers to recover security-sensitive values generated by WordArray.random(). The function seeds a custom Multiply-With-Carry generator from Math.random(), reducing nominal 128-bit and 256-bit outputs to roughly 39-bit and 47-bit search spaces. Exploitation requires an application to use this function for secrets; enumeration can expose wallet recovery phrases and private keys, while dependency alone is insufficient.
Summary
What happened
Insufficient entropy in Brix crypto-js before 4.0.0 allows attackers to recover security-sensitive values generated by WordArray.random(). The function seeds a custom Multiply-With-Carry generator from Math.random(), reducing nominal 128-bit and 256-bit outputs to roughly 39-bit and 47-bit search spaces. Exploitation requires an application to use this function for secrets; enumeration can expose wallet recovery phrases and private keys, while dependency alone is insufficient.
The record
- CVE
- CVE-2026-71851
- Published
- Aug 7, 2026
- Updated
- Aug 7, 2026
- Vendor
- Brix
- Product
- crypto-js
- Classifications
- CWE-331, CWE-338, CWE-334, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 7, 2026CVE publishedPublication date reported by the CVE source.
- Aug 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Ill Bloom end-to-end secret-recovery proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- Ill Bloom active wallet-drain exploitationreported exploitation
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo