# CVE-2026-69108: Privilege escalation in Siemens License Server (SLS)

> Local attackers can exploit insecure sudoers policies in Siemens License Server to execute arbitrary commands as root, achieving full system compromise.

- **Severity:** High 8.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-gc42-c48g-89rf

## What is CVE-2026-69108?

CVE-2026-69108 is a high-severity vulnerability in Siemens License Server (SLS), published on 11 Aug 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 Siemens License Server (SLS) (All versions < V5.1). The affected application is vulnerable to a local privilege escalation due to an insecure sudoers policy. This could allow an attacker to execute arbitrary commands and plant malicious files as root, leading to full system compromise.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2026-69108 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69108 is a high-severity vulnerability in Siemens License Server (SLS), published on 11 Aug 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-69108 in the wild and no public exploit code.

Affected product: Siemens License Server (SLS). 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-69108/ (Markdown: https://insights.sbomify.com/CVE-2026-69108/index.md)
```

## Sources

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

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