# CVE-2026-50093: File upload in Siveillance Control Pro V3.0

> An arbitrary file upload vulnerability in the OIS web module allows attackers to gain root access and fully compromise the system.

- **Severity:** High 8.9 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-2rpg-jwp8-r64m

## What is CVE-2026-50093?

CVE-2026-50093 is a high-severity vulnerability in Siemens Siveillance Control Pro V3.0, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been identified in Siveillance Control Pro V3.0 (All versions < V3.0.12.2173), Siveillance Control Pro V4.0 (All versions < V4.0.9.2178), Siveillance Control V3.0 (All versions < V3.0.22.2177), Siveillance Control V4.0 (All versions < V4.0.11.2177). A vulnerability in the OIS web module allows an attacker to upload arbitrary files to the server. Successful exploitation of this vulnerability could allow an attacker to gain root access on the host system, potentially leading to a full compromise of the affected OIS environment.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-50093 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50093 is a high-severity vulnerability in Siemens Siveillance Control Pro V3.0, published on 8 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50093 in the wild and no public exploit code.

Affected product: Siemens Siveillance Control Pro V3.0. 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-50093/ (Markdown: https://insights.sbomify.com/CVE-2026-50093/index.md)
```

## Sources

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

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