XDG Desktop Portal CVE-2026-55888

Requires an attacker-controlled malicious or compromised sandboxed application (e.g., a Flatpak app) running under xdg-desktop-portal prior to version 1.22.1. That app calls the FileChooser.SaveFiles method supplying the optional 'files' filenames containing path-traversal components; because the filenames are validated neither by the frontend nor by common backends, they are appended to the user-selected directory and written to the host. Limiting factors: exploitation is bounded to creating files that do NOT already exist (existing files cannot be overwritten) and only in locations the invoking user already has write access to; it also depends on the user engaging the file save dialog, and on the deployment using an affected backend that performs no filename validation.

The vendor CVSS 4.0 score is 8.8 (High), driven by VI:H and an AV:N/PR:N/UI:N framing, but several signals temper the real-world urgency. No EPSS score was provided, the CVE is not in CISA KEV (not confirmed actively exploited), and no public exploit reference is supplied - the only references are the GHSA advisory and the 1.22.1 release notes. The vuln.today decision label is 'this_week', consistent with a serious-but-not-emergency flaw: patch promptly, but this is not an act_now/emergency case. The most important caveat is that the vendor vector appears to overstate reach: xdg-desktop-portal is a local D-Bus service, and exploitation requires the attacker to already be running a malicious/compromised sandboxed (Flatpak) application and the user to operate a file save dialog - this maps far better to a local vector with user interaction than to AV:N/UI:N, so the 'remote unauthenticated network' reading should be verified against the local sandbox-escape mechanism described. Impact is further bounded: writes are limited to files that do not already exist and only to paths the invoking user can access (no overwrite of existing files). Net assessment: a genuine sandbox-escape integrity issue worth patching this week, but the 8.8 headline overstates the practical attack surface given the malicious-app precondition and the inability to overwrite existing files.

A user installs or runs a malicious or trojanized sandboxed (Flatpak) application. The app invokes FileChooser.SaveFiles with the optional 'files' option containing filenames that include path-traversal sequences; because neither the frontend nor common backends validate them, the backend appends them to the user-selected directory and creates a new file outside the sandbox - for example an autostart .desktop entry or a shell startup file in a location the user can write - enabling later code execution. No public exploit code is identified at time of analysis.