# CVE-2026-110217: vhr through commit 03abbd3 Information Disclosure of Operator Password Hashes via GET /chat/hrs

> Authenticated users can retrieve other operators' password hashes and personal data, enabling offline cracking and privilege escalation.

- **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`)
- **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:** 13 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-9r96-j8cv-gv8g

## What is CVE-2026-110217?

CVE-2026-110217 is a high-severity vulnerability in lenve vhr, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Lenve vhr through commit 03abbd3 contains an information disclosure vulnerability that allows any authenticated user to retrieve other operators' BCrypt password hashes via GET /chat/hrs. Low-privileged operators can collect administrator password hashes, phone numbers, and addresses from the serialized Hr entity for offline cracking and privilege escalation.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-110217 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110217 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110217 is a high-severity vulnerability in lenve vhr, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110217 exists.

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

## Sources

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

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