# CVE-2026-110216: youlai-boot through 2.21.1 Missing Authorization in User Status Update Endpoint

> Authenticated users can modify account statuses without authorization, potentially locking out administrators or re-enabling disabled accounts.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/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:** 13 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-6cm8-g463-wr86

## What is CVE-2026-110216?

CVE-2026-110216 is a high-severity missing authorization vulnerability in youlaitech youlai-boot, published on 13 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

youlai-boot through 2.21.1 contains a missing authorization vulnerability that allows any authenticated user to enable or disable accounts because the updateUserStatus handler lacks a @PreAuthorize check. Attackers can send PATCH requests to /api/v1/users/{userId}/status to disable root or admin accounts, locking administrators out, or re-enable accounts an administrator has disabled.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-110216 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110216 is a high-severity missing authorization vulnerability in youlaitech youlai-boot, published on 13 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-110216 in the wild and no public exploit code.

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

## Sources

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

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