# CVE-2026-108650: JeecgBoot through 3.9.5 Missing Authorization via /sys/api/getUserPermissionSet

> Authenticated users can read other users' permission codes by supplying arbitrary user IDs, exposing sensitive access control data.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-2326-787x-9j94

## What is CVE-2026-108650?

CVE-2026-108650 is a medium-severity missing authorization vulnerability in JeecgBoot, published on 10 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

JeecgBoot through 3.9.5 contains a missing authorization vulnerability in the getUserPermissionSet handler of SystemApiController that allows any authenticated user to read other users' permission codes. Low-privileged attackers can supply an arbitrary userId to GET /sys/api/getUserPermissionSet to retrieve the full permission set of any account, including administrators.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-108650 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108650 is a medium-severity missing authorization vulnerability in JeecgBoot, published on 10 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-108650 exists.

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

## Sources

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

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