# CVE-2026-109185: jshERP through 3.6 Privilege Escalation via PUT /user/updateUser

> Authenticated users can escalate privileges to tenant administrator by manipulating role assignments in the user update endpoint.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/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:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-jc6r-cm4g-j9v8

## What is CVE-2026-109185?

CVE-2026-109185 is a high-severity vulnerability in jishenghua jshERP, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

jshERP through 3.6 contains a missing authorization vulnerability in the UserController updateUser handler that allows authenticated users to assign arbitrary roles to any user. Low-privilege attackers can send their own user id with the tenant administrator roleId to escalate privileges or rebind other tenant users' roles.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-109185 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109185 is a high-severity vulnerability in jishenghua jshERP, published on 12 Oct 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-109185 in the wild and no public exploit code.

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

## Sources

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

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