# CVE-2022-41975: Privilege escalation in n/a

> Local attackers can escalate privileges on Windows systems by exploiting the MSI installer Repair mode in RealVNC software.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A: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:** 30 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** GHSA-vx7g-xm5j-vv7c

## What is CVE-2022-41975?

CVE-2022-41975 is a high-severity vulnerability in n/a, published on 30 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RealVNC VNC Server before 6.11.0 and VNC Viewer before 6.22.826 on Windows allow local privilege escalation via MSI installer Repair mode.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 2 products.


Products: Realvnc Vnc Server, Realvnc Vnc Viewer.

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

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

## Is CVE-2022-41975 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-27502](https://insights.sbomify.com/CVE-2022-27502/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41975 is a high-severity vulnerability in n/a, published on 30 Sep 2022. 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-41975 in the wild and no public exploit code.

Affected product: n/a. 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-41975/ (Markdown: https://insights.sbomify.com/CVE-2022-41975/index.md)
```

## Sources

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

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