# CVE-2026-22104: Improper access control in Hashtopolis server chunk activity component

> Any authenticated user can read all cracked hashes due to improper access control in the chunk activity component.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/R:I`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-mr39-qwfq-3rmh

## What is CVE-2026-22104?

CVE-2026-22104 is a high-severity missing authorization vulnerability in hashtopolis server, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper access control in Hashtopolis server web-interface chunk activity component for versions prior to 0.14.8 allows any created account to read all cracked hashes of a Hashtopolis server instance.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-22104 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-22104 is a high-severity missing authorization vulnerability in hashtopolis server, published on 17 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22104 in the wild and no public exploit code.

Affected product: hashtopolis server. 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-22104/ (Markdown: https://insights.sbomify.com/CVE-2026-22104/index.md)
```

## Sources

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

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