# CVE-2026-93971: aiyiyi121 SxDevOps settings.py information disclosure

> Remote attackers can access sensitive information from the SxDevOps settings file, requiring a patch to mitigate the disclosure risk.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-68r3-599r-wq4c

## What is CVE-2026-93971?

CVE-2026-93971 is a medium-severity vulnerability in aiyiyi121 SxDevOps, published on 20 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in aiyiyi121 SxDevOps 1.0/1.1. Impacted is an unknown function of the file backend/sxdevops/settings.py. This manipulation causes information disclosure. It is possible to initiate the attack remotely. Patch name: 2b4bf8585c3e731e7a8af30801ea46680bc783f9. It is suggested to install a patch to address 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-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-93971 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93971 is a medium-severity vulnerability in aiyiyi121 SxDevOps, published on 20 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93971 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-93971/ (Markdown: https://insights.sbomify.com/CVE-2026-93971/index.md)
```

## Sources

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

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