EUVD-2026-26003Severity by source
AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L
Lifecycle Timeline
6DescriptionCVE.org
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.)
AnalysisAI
KDE Dolphin before 25.12.3 allows sandboxed applications (running under Flatpak or AppArmor confinement) to bypass sandbox restrictions and open arbitrary files outside their containment boundary through the FileManager1 D-Bus protocol implementation. An attacker controlling a sandboxed application can exploit this to access sensitive files or execute scripts with user interaction, circumventing the intended isolation model.
Technical ContextAI
KDE Dolphin implements the FileManager1 D-Bus protocol, a system-level service that allows applications to request file manager operations. The vulnerability exists because Dolphin's protocol handler accepts arbitrary file paths without validating whether the requesting application has sandbox permission to access those paths. CWE-669 (Incorrect Resource Transfer Between Spheres) describes the root cause: resources (file paths) are transferred from a confined application context to an unconfined file manager without proper boundary enforcement. When a Flatpak or AppArmor-confined application calls FileManager1 methods with an absolute path, Dolphin opens that path in its own context, which runs outside the sandbox and thus has access to the host filesystem. The implementation compounds the risk by defaulting to a user-consent prompt for executable files rather than a deny-by-default policy.
RemediationAI
Upgrade KDE Dolphin to version 25.12.3 or later immediately. The fix is confirmed released at https://github.com/KDE/dolphin/releases/tag/v25.12.3 and documented in the KDE security advisory at https://kde.org/info/security/advisory-20260427-2.txt. For distributions packaging older versions, request backported security updates. If immediate upgrade is not feasible, mitigate by restricting the scope of Flatpak applications permitted to run on the system - whitelist only trusted applications from official repositories and disable sideloaded or third-party Flatpak sources, which reduces the likelihood of a malicious sandboxed application being installed. Organizations relying on AppArmor can audit sandbox profiles to ensure Dolphin runs with appropriate confinement; however, this is a defense-in-depth measure and does not replace the patch. Users should avoid running untrusted applications in Flatpak sandboxes until patched, as the sandbox is no longer a reliable security boundary for file access in affected Dolphin versions.
Cross-site request forgery (CSRF) vulnerability in administration/profiles.php in Dolphin 7.1.4 and earlier allows remot
SQL injection vulnerability in administration/profiles.php in BoonEx Dolphin 7.1.4 and earlier allows remote authenticat
Multiple cross-site scripting (XSS) vulnerabilities in Boonex Dolphin before 7.0.8 allow remote attackers to inject arbi
The Backup and Restore feature in Mobotap Dolphin Browser for Android 12.0.2 suffers from an arbitrary file write vulner
Dolphin CMS 7.4.2 is vulnerable to stored XSS via the Page Builder "width" parameter. Rated medium severity (CVSS 4.8),
The Dolphin Browser for Android 12.0.2 suffers from an insecure parsing implementation of the Intent URI scheme. Rated m
Same technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today