# CVE-2026-119647: RuoYi-Vue-Plus through 6.0.0 Data-Scope Bypass via /system/user/list/dept/{deptId}


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-67wx-v635-xxc9

## What is CVE-2026-119647?

CVE-2026-119647 is a medium-severity vulnerability in dromara RuoYi-Vue-Plus, published on 30 Oct 2026. 

### Official description

RuoYi-Vue-Plus through 6.0.0 contains an authorization bypass vulnerability in SysUserServiceImpl.selectUserListByDept that allows authenticated users to read users of other departments. Users holding system:user:list under a department-restricted role can request GET /system/user/list/dept/{deptId} with any department id to obtain usernames, nicknames, account status, last login IP and time, and remarks.

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

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


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

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

## Is CVE-2026-119647 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119647 is a medium-severity vulnerability in dromara RuoYi-Vue-Plus, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119647 in the wild and no public exploit code.

Affected product: dromara RuoYi-Vue-Plus. 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-119647/ (Markdown: https://insights.sbomify.com/CVE-2026-119647/index.md)
```

## Sources

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

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