# CVE-2026-53406: Privilege escalation in Remote Control for Zoom Contact Center

> An authenticated local user can escalate privileges in Zoom Contact Center for Windows due to insufficient data authenticity verification.

- **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:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-789h-4f4q-2gq6

## What is CVE-2026-53406?

CVE-2026-53406 is a high-severity vulnerability in Remote Control for Zoom Contact Center, published on 12 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insufficient Verification of Data Authenticity in Remote Control for Zoom Contact Center for Windows before version 7.0.0 may allow an authenticated user to enable an escalation of privilege via local access.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Zoom Remote Control.

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

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

## Is CVE-2026-53406 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53406 is a high-severity vulnerability in Remote Control for Zoom Contact Center, published on 12 Jun 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-53406 in the wild and no public exploit code.

Affected product: Remote Control for Zoom Contact Center. 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-53406/ (Markdown: https://insights.sbomify.com/CVE-2026-53406/index.md)
```

## Sources

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

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