# CVE-2026-88620: Missing authorization in n/a

> An authenticated low-privileged user can access employee records from other departments due to missing authorization checks in the API.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 15 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-66fq-wqr6-g245

## What is CVE-2026-88620?

CVE-2026-88620 is a medium-severity missing authorization vulnerability in n/a, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SmartAdmin API Java17 SpringBoot3 version 3.30.0 contains an improper authorization vulnerability in the /employee/queryAll endpoint. The endpoint does not enforce the required function-level permission or data-scope authorization, allowing an authenticated low-privileged employee to retrieve employee records belonging to other departments and users

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-88620 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88620 is a medium-severity missing authorization vulnerability in n/a, published on 15 Sep 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-88620 in the wild and no public exploit code.

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

## Sources

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

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