# CVE-2026-41527: Privilege escalation in Kleopatra

> Local attackers can escalate privileges to that of a Kleopatra user due to a flaw in the single-instance enforcement mechanism on Windows.

- **Severity:** Medium 6.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2026
- **Updated:** 22 Apr 2026
- **Also known as:** GHSA-g2r2-6v8v-5qgm

## What is CVE-2026-41527?

CVE-2026-41527 is a medium-severity vulnerability in KDE Kleopatra, published on 21 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

KDE Kleopatra before 26.08.0 on Windows allows local users to obtain the privileges of a Kleopatra user, because there is an error in the mechanism (KUniqueService) for ensuring that only one instance is running.

Weakness: CWE-670 (Always-Incorrect Control Flow Implementation)

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


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

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

## Is CVE-2026-41527 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41527 is a medium-severity vulnerability in KDE Kleopatra, published on 21 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-41527 in the wild and no public exploit code.

Affected product: KDE Kleopatra. 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-41527/ (Markdown: https://insights.sbomify.com/CVE-2026-41527/index.md)
```

## Sources

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

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