# CVE-2026-111330: JuggleIM im-server through 1.8.16 Weak Password Hashing via Unsalted SHA-1

> Attackers with database access can crack admin console passwords stored as unsalted SHA-1 hashes, leading to account takeover.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-53gf-xhq2-c3j8

## What is CVE-2026-111330?

CVE-2026-111330 is a high-severity vulnerability in JuggleIM, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

## Which versions are affected by CVE-2026-111330?


## How do I fix CVE-2026-111330?

No fix has been published for CVE-2026-111330 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111330 being exploited?

There is no known exploitation of CVE-2026-111330 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111330 and fix it if it is affected.

What it is: CVE-2026-111330 is a high-severity vulnerability in JuggleIM, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111330 in the wild and no public exploit code.

Affected product: JuggleIM. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111330/ (Markdown: https://insights.sbomify.com/CVE-2026-111330/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111330
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111330
- OSV: https://osv.dev/vulnerability/CVE-2026-111330

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111330/
Summaries are generated and may contain mistakes; the official description above is the record.