# CVE-2026-110633: MyReport Updater through 2.1.1 Local Privilege Escalation via Updater Service

> Low-privileged users can escalate to SYSTEM privileges by manipulating the updater service to install malicious DLLs via gRPC.

- **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:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-www7-gw3x-qcrq

## What is CVE-2026-110633?

CVE-2026-110633 is a high-severity vulnerability in MyReport Updater, published on 14 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MyReport Updater through 2.1.1 contains a local privilege escalation vulnerability that allows low-privileged users to make the SYSTEM updater service install attacker-supplied archives into arbitrary directories. Attackers can use UpdaterManager.exe over gRPC to set a malicious reference server and installLocation, planting a DLL like HID.dll loaded by osk.exe to gain SYSTEM privileges.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-110633 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110633 is a high-severity vulnerability in MyReport Updater, published on 14 Oct 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-110633 in the wild and no public exploit code.

Affected product: MyReport Updater. 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-110633/ (Markdown: https://insights.sbomify.com/CVE-2026-110633/index.md)
```

## Sources

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

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