CVE-2026-111330 json
JuggleIM im-server through 1.8.16 Weak Password Hashing via Unsalted SHA-1
published 2026-10-15 24 d ago modified 2026-10-16 23 d ago also EUVD-2026-102484
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
JuggleIM im-server through 1.8.16 contains a weak password hashing vulnerability that stores admin console passwords as unsalted SHA-1 digests via tools.SHA1 in services/accountservice.go. Attackers who obtain the accounts table through database access or backups can crack console passwords using precomputed tables or GPU brute force.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 23 d ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- juggleim JuggleIM
Classification
- Weakness
-
- CWE-916 Use of Password Hash With Insufficient Computational Effort
References
-
hackmd.io
/@hieuPenguinnn/juggleim-im-server-default-admin-credential
third-party-advisory
-
github.com
/juggleim/imserver-console/blob/v1.0.10/services/accountservice.go#L95
technical-description
-
github.com
/juggleim/im-server/blob/v1.8.16/sql/imserver.sql#L3-L15
technical-description
-
github.com
/juggleim/im-server
product
-
vulncheck.com
/advisories/juggleim-im-server-through-1.8.16-weak-password-hashing-via-unsalted-sha-1
third-party-advisory
Sources
- CVE List CVE-2026-111330
- NVD CVE-2026-111330
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.