# CVE-2026-93968: aiyiyi121 SxDevOps UserSerializer serializers.py update privileges management

> Remote attackers can exploit improper privilege management in the UserSerializer update function to escalate privileges within the SxDevOps application.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-4q5m-2j7g-wf56

## What is CVE-2026-93968?

CVE-2026-93968 is a medium-severity vulnerability in aiyiyi121 SxDevOps, published on 20 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was determined in aiyiyi121 SxDevOps 1.0/1.1. This affects the function update of the file backend/rbac/serializers.py of the component UserSerializer. Executing a manipulation can lead to improper privilege management. The attack can be executed remotely. This patch is called 2b4bf8585c3e731e7a8af30801ea46680bc783f9. It is best practice to apply a patch to resolve this issue. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

Weakness: CWE-269 (Improper Privilege Management), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-93968 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93968 is a medium-severity vulnerability in aiyiyi121 SxDevOps, published on 20 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93968 in the wild and no public exploit code.

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

## Sources

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

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