# CVE-2022-50927: Cyclades Serial Console Server 3.3.0 - Local Privilege Escalation

> Attackers with local access can gain root privileges by exploiting overly permissive sudo configurations in the Cyclades Serial Console Server.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 13 Jan 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-w5q8-rwwv-x78m

## What is CVE-2022-50927?

CVE-2022-50927 is a high-severity vulnerability in Vertiv Cyclades Serial Console Server, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cyclades Serial Console Server 3.3.0 contains a local privilege escalation vulnerability due to overly permissive sudo privileges for the admin user and admin group. Attackers can exploit the default user configuration to gain root access by manipulating system binaries and leveraging unrestricted sudo permissions.

Weakness: CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2022-50927?


## How do I fix CVE-2022-50927?

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

## Is CVE-2022-50927 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50927 and fix it if it is affected.

What it is: CVE-2022-50927 is a high-severity vulnerability in Vertiv Cyclades Serial Console Server, published on 13 Jan 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-2022-50927 in the wild and no public exploit code.

Affected product: Vertiv Cyclades Serial Console Server. 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-2022-50927/ (Markdown: https://insights.sbomify.com/CVE-2022-50927/index.md)
```

## Sources

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

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