# CVE-2026-110632: Report One MyReport Updater through 2.1.1 Unauthenticated gRPC Service RCE

> Unauthenticated gRPC service allows attackers to redirect the updater to malicious servers, achieving remote code execution as SYSTEM.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-c58m-4p4j-mrrh

## What is CVE-2026-110632?

CVE-2026-110632 is a critical missing authorization vulnerability in MyReport Updater, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Report One MyReport Updater through 2.1.1 exposes an unauthenticated gRPC service on TCP port 9095 that allows remote attackers to redirect the SYSTEM updater by invoking the UpdateConfigReferent method. Attackers can point the updater to a malicious reference server serving modified module archives with matching MD5 digests to write files and execute code as SYSTEM.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-110632 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110632 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110632 is a critical missing authorization vulnerability in MyReport Updater, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110632 exists.

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-110632/ (Markdown: https://insights.sbomify.com/CVE-2026-110632/index.md)
```

## Sources

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

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