CVE-2026-41525: 
Linux Debian vulnerability analysis and mitigation

CVE-2026-41525 is a sandbox bypass vulnerability in KDE Dolphin file manager that allows applications running inside a Flatpak sandbox or under AppArmor confinement to open files outside the application sandbox without proper scrutiny. Dolphin's implementation of the org.freedesktop.FileManager1.ShowFolders D-Bus protocol accepts any file path — including scripts or executables — rather than restricting input to directories as intended. Instead of blocking such attempts, Dolphin incorrectly presents the user with a consent prompt, which can be leveraged to execute arbitrary code. All KDE Dolphin versions before 25.12.3 are affected. It was publicly disclosed on April 28, 2026, and carries a CVSS v3.1 base score of 6.5 (Medium) (Red Hat Advisory, GitHub Advisory).

The root cause is classified under CWE-669 (Incorrect Resource Transfer Between Spheres) and CWE-807 (Reliance on Untrusted Inputs in a Security Decision). Dolphin's FileManager1 D-Bus interface (org.freedesktop.FileManager1.ShowFolders) is intended to accept only directory URIs, but it fails to validate that the provided path is actually a directory before processing it. A sandboxed application can invoke this D-Bus method with a file:// URI pointing to a script or executable outside the sandbox; Dolphin then presents a user prompt asking whether to launch the file rather than silently rejecting the request, which is the correct behavior. This design flaw means the sandbox boundary is effectively bypassed with only user interaction required, not additional privileges (Red Hat Bugzilla, oss-security).

Successful exploitation allows a confined application to escape its sandbox and potentially execute arbitrary scripts or executables on the host system with the privileges of the user running Dolphin. This results in high confidentiality and integrity impact — an attacker could read or modify files outside the sandbox — and low availability impact. The attack is local and requires user interaction (the user must accept the Dolphin prompt), limiting its scope, but a socially engineered user could inadvertently authorize execution of malicious code delivered from within a sandboxed application (GitHub Advisory, Red Hat Bugzilla).

There is no public proof-of-concept exploit code and no evidence of in-the-wild exploitation as of the time of disclosure (GitHub Advisory). The EPSS score is approximately 0.012% (4th percentile), indicating a very low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Exploitation requires local access, high attack complexity, and user interaction, which significantly reduces practical exploitability (GitHub Advisory).

1. Prepare malicious payload: From within a Flatpak-sandboxed or AppArmor-confined application, write a malicious script or executable to a location accessible via a file:// URI (e.g., /tmp/malware.sh).
2. Invoke FileManager1 D-Bus method: Use the D-Bus session bus to call org.freedesktop.FileManager1.ShowFolders with the URI of the malicious file (e.g., file:///tmp/malware.sh) as the argument, bypassing the sandbox's D-Bus restrictions since this interface is accessible to confined apps.
3. Trigger Dolphin prompt: Dolphin receives the request and, instead of rejecting the non-directory path, presents the user with a dialog asking whether they want to launch the script or executable.
4. Social engineering: The attacker relies on the user accepting the prompt (e.g., by disguising the file as a legitimate folder or document), causing Dolphin to execute the payload outside the sandbox with the user's full privileges (oss-security, Red Hat Bugzilla).

• D-Bus Activity: Unexpected org.freedesktop.FileManager1.ShowFolders D-Bus calls originating from a Flatpak or AppArmor-confined application with non-directory file:// URIs as arguments.
• Process: Unusual child processes spawned by the Dolphin file manager process (e.g., shell interpreters, script runners, or unexpected executables) that are not typical file manager operations.
• File System: Presence of unexpected scripts or executables in world-writable directories (e.g., /tmp/, ~/.local/share/) that may have been staged by a sandboxed application.
• Logs: AppArmor or audit logs showing a confined application accessing D-Bus session bus methods outside its expected profile; Dolphin application logs showing attempts to open non-directory paths via the FileManager1 interface.

Upgrade KDE Dolphin to version 25.12.3 or later, which corrects the FileManager1 protocol handler to block non-directory paths rather than prompting the user (KDE Dolphin Release, KDE Advisory). As a workaround for systems that cannot immediately upgrade, administrators can deploy a D-Bus shim (such as the one developed by the Kicksecure project) that intercepts org.freedesktop.FileManager1 calls and validates that all provided URIs point to real directories before forwarding them (oss-security). Additionally, restricting sandboxed applications' access to the D-Bus session bus via stricter AppArmor D-Bus mediation or xdg-dbus-proxy policies can reduce exposure.

Security researcher Aaron Rainbolt published a detailed analysis on the oss-security mailing list in May 2026, contextualizing CVE-2026-41525 within a broader class of D-Bus sandbox escape issues affecting multiple Linux desktop components, including PCManFM-Qt and Wine's MIME handler registrations (oss-security). The post highlighted that the Kicksecure project had already developed a D-Bus shim as a mitigation and called on maintainers of applications that execute code to audit their MIME handler registrations. Red Hat triaged the issue at high severity in their Bugzilla tracker (Red Hat Bugzilla).