# CVE-2026-85182: vhr Missing Authorization in PUT /hr/pass Allows Cross-Account Password Change

> Authenticated attackers can change arbitrary account passwords in the vhr HR system due to missing authorization checks on the password update endpoint.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 3 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-q54m-q6wq-qhwg

## What is CVE-2026-85182?

CVE-2026-85182 is a high-severity missing authorization vulnerability in lenve vhr, published on 3 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

vhr through commit 03abbd3 fails to verify that the account ID in PUT /hr/pass requests belongs to the authenticated caller. Authenticated attackers can change arbitrary account passwords by supplying a target account ID and that account's current password in the request body.

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

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


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

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

## Is CVE-2026-85182 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85182 is a high-severity missing authorization vulnerability in lenve vhr, published on 3 Sep 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-85182 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-85182/ (Markdown: https://insights.sbomify.com/CVE-2026-85182/index.md)
```

## Sources

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

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