# CVE-2026-0539: Local Privilege Escalation in pcvisit service client

> A local attacker can escalate privileges to SYSTEM by overwriting the pcvisit service binary due to incorrect default permissions.

- **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:** 22 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-327c-mq4q-4h9h

## What is CVE-2026-0539?

CVE-2026-0539 is a high-severity vulnerability in pcvisit Remote Host Modul, published on 22 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect Default Permissions in pcvisit service binary on Windows allows a low-privileged local attacker to escalate their privileges by overwriting the service binary with arbitrary contents. This service binary is automatically launched with NT\SYSTEM privileges on boot. This issue affects all versions after 22.6.22.1329 and was fixed in 25.12.3.1745.

Weakness: CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2026-0539 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-0539 is a high-severity vulnerability in pcvisit Remote Host Modul, published on 22 Apr 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-0539 in the wild and no public exploit code.

Affected product: pcvisit Remote Host Modul. 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-0539/ (Markdown: https://insights.sbomify.com/CVE-2026-0539/index.md)
```

## Sources

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

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