CVE-2025-54885: simbo1905 thinbus-srp-npm · Insufficient Entropy
Affects simbo1905 thinbus-srp-npmSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 2.0.1 when convenient.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.0.1
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 7 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade simbo1905 thinbus-srp-npm to 2.0.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| simbo1905 thinbus-srp-npm | Affected
| Fixed in
|
AI-suggested
European organizations should immediately audit their software dependencies to identify usage of thinbus-srp-npm versions below 2.0.1. Upgrading to version 2.0.1 or later is the primary and most effective mitigation, as it corrects the entropy generation flaw. For applications where immediate upgrade is not feasible, organizations should consider implementing compensating controls such as additional multi-factor authentication layers to reduce the risk of compromised credentials. Monitoring authentication logs for unusual patterns or repeated failed attempts can help detect exploitation attempts. Developers should review their implementation of SRP protocols to ensure compliance with specifications and proper entropy sources. Additionally, organizations should conduct penetration testing focused on authentication mechanisms to validate the effectiveness of mitigations. Finally, educating development teams about cryptographic best practices and the importance of using well-maintained libraries can prevent similar issues.
Description
Thinbus Javascript Secure Remote Password is a browser SRP6a implementation for zero-knowledge password authentication. In versions 2.0.0 and below, a protocol compliance bug causes the client to generate a fixed 252 bits of entropy instead of the intended bit length of the safe prime (defaulted to 2048 bits). The client public value is being generated from a private value that is 4 bits below the specification. This reduces the protocol's designed security margin it is now practically exploitable. The servers full sized 2048 bit random number is used to create the shared session key and password proof. This is fixed in version 2.0.1.