# CVE-2026-111324: rustdesk-api through 2.7 Authorization Bypass via POST /api/sysinfo

> Unauthenticated attackers can overwrite peer records and rebind devices to their accounts by exploiting missing verification in the sysinfo endpoint.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/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:** 15 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-qvc9-rg5c-3453

## What is CVE-2026-111324?

CVE-2026-111324 is a medium-severity authentication bypass vulnerability in lejianwen rustdesk-api, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

rustdesk-api through 2.7 contains an authorization bypass vulnerability that allows unauthenticated attackers to overwrite existing peer records by supplying only a target device ID to POST /api/sysinfo. Attackers can overwrite hostname, username, OS and uuid without uuid verification, then log in presenting that uuid to rebind the peer to their account.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111324 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111324 is a medium-severity authentication bypass vulnerability in lejianwen rustdesk-api, published on 15 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-111324 exists.

Affected product: lejianwen rustdesk-api. 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-111324/ (Markdown: https://insights.sbomify.com/CVE-2026-111324/index.md)
```

## Sources

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

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