# CVE-2025-66576: Remote Keyboard Desktop 1.0.1 - Remote Code Execution (RCE)

> Remote attackers can execute arbitrary system commands on Remote Keyboard Desktop via an unauthenticated vulnerability in the rundll32.exe export.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-7q3r-f5rw-p7gp

## What is CVE-2025-66576?

CVE-2025-66576 is a high-severity command injection vulnerability in Remotecontrolio Remote Keyboard Desktop, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Remote Keyboard Desktop 1.0.1 enables remote attackers to execute system commands via the rundll32.exe exported function export, allowing unauthenticated code execution.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2025-66576?

It affects 1 product.


Products: Remotecontrolio Remote Keyboard Desktop.

## How do I fix CVE-2025-66576?

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

## Is CVE-2025-66576 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-66576 and fix it if it is affected.

What it is: CVE-2025-66576 is a high-severity command injection vulnerability in Remotecontrolio Remote Keyboard Desktop, published on 4 Dec 2025. 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-2025-66576 exists.

Affected product: Remotecontrolio Remote Keyboard Desktop. 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-2025-66576/ (Markdown: https://insights.sbomify.com/CVE-2025-66576/index.md)
```

## Sources

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

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