# CVE-2026-41525: Security feature bypass in Dolphin

> KDE Dolphin allows sandboxed applications to open arbitrary files, bypassing confinement restrictions by prompting users instead of blocking actions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Apr 2026
- **Updated:** 19 May 2026
- **Also known as:** DEBIAN-CVE-2026-41525, GHSA-53j4-26mm-gcr3, UBUNTU-CVE-2026-41525

## What is CVE-2026-41525?

CVE-2026-41525 is a medium-severity vulnerability in KDE Dolphin, published on 28 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

KDE Dolphin before 25.12.3 allows applications in a Flatpak (or with AppArmor confinement) to open folders outside of the application sandbox without additional scrutiny. Dolphin's implementation of the FileManager1 protocol allows the path given to be any type of file, including scripts or executables. (By default, Dolphin will then prompt the user to determine if they want to launch a script or executable; however, the intended behavior is to block the attempted action, not present a consent prompt.)

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

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


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

Upgrade to a fixed version.

## Is CVE-2026-41525 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41525 is a medium-severity vulnerability in KDE Dolphin, published on 28 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41525 in the wild and no public exploit code.

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

## Sources

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

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