Flatpak is a Linux application sandboxing and distribution framework. Prior to versions 1.14.0 and 1.15.10, a malicious or compromised Flatpak app using persistent directories could access and write files outside of what it would otherwise have access to, which is an attack on integrity and confidentiality. When `persistent=subdir` is used in the application permissions (represented as `--persist=subdir` in the command-line interface), that means that an application which otherwise doesn't have access to the real user home directory will see an empty home directory with a writeable subdirectory `subdir`. Behind the scenes, this directory is actually a bind mount and the data is stored in the per-application directory as `~/.var/app/$APPID/subdir`. This allows existing apps that are not aware of the per-application directory to still work as intended without general home directory access. However, the application does have write access to the application directory `~/.var/app/$APPID` where this directory is stored. If the source directory for the `persistent`/`--persist` option is replaced by a symlink, then the next time the application is started, the bind mount will follow the symlink and mount whatever it points to into the sandbox. Partial protection against this vulnerability can be provided by patching Flatpak using the patches in commits ceec2ffc and 98f79773. However, this leaves a race condition that could be exploited by two instances of a malicious app running in parallel. Closing the race condition requires updating or patching the version of bubblewrap that is used by Flatpak to add the new `--bind-fd` option using the patch and then patching Flatpak to use it. If Flatpak has been configured at build-time with `-Dsystem_bubblewrap=bwrap` (1.15.x) or `--with-system-bubblewrap=bwrap` (1.14.x or older), or a similar option, then the version of bubblewrap that needs to be patched is a system copy that is distributed separately, typically `/usr/bin/bwrap`. This configuration is the one that is typically used in Linux distributions. If Flatpak has been configured at build-time with `-Dsystem_bubblewrap=` (1.15.x) or with `--without-system-bubblewrap` (1.14.x or older), then it is the bundled version of bubblewrap that is included with Flatpak that must be patched. This is typically installed as `/usr/libexec/flatpak-bwrap`. This configuration is the default when building from source code. For the 1.14.x stable branch, these changes are included in Flatpak 1.14.10. The bundled version of bubblewrap included in this release has been updated to 0.6.3. For the 1.15.x development branch, these changes are included in Flatpak 1.15.10. The bundled version of bubblewrap in this release is a Meson "wrap" subproject, which has been updated to 0.10.0. The 1.12.x and 1.10.x branches will not be updated for this vulnerability. Long-term support OS distributions should backport the individual changes into their versions of Flatpak and bubblewrap, or update to newer versions if their stability policy allows it. As a workaround, avoid using applications using the `persistent` (`--persist`) permission.
When a Flatpak application uses the `persistent=subdir` permission, a bind mount is created behind the scenes linking a subdirectory visible in the sandbox with the actual location `~/.var/app/$APPID/subdir`. Since the application has write permissions to the `~/.var/app/$APPID` directory, it can replace the source directory of the `--persist` option with a symlink pointing anywhere in the filesystem. On the next launch, the bind mount will follow the symlink and mount the indicated directory inside the sandbox, giving the application access to areas it should not have permissions for. Even partial Flatpak patching leaves a race condition exploitable by two parallel instances of a malicious application — full remediation requires updating both Flatpak and the cooperating bubblewrap tool (adding the `--bind-fd` option).
An attacker can read and overwrite user files beyond the boundaries of the Flatpak sandbox, resulting in violation of data confidentiality and integrity — potentially including sensitive configuration files, private keys, or other data stored in the home directory.
Update Flatpak to version 1.14.10 (stable branch) or 1.15.10 (developer branch), which contain the necessary patches along with updated bubblewrap (0.6.3 and 0.10.0 respectively). In configurations with system-wide bubblewrap copy (`/usr/bin/bwrap`), updating the system bubblewrap package is also required. LTS distributions should backport changes from commits indicated by the vendor. As a workaround, avoid applications using the `persistent` permission (`--persist`) until patches are applied.
Flatpak versions earlier than 1.14.10 (stable branch 1.14.x) and earlier than 1.15.10 (developer branch 1.15.x). Branches 1.12.x and 1.10.x will not receive updates. Also affects Debian Linux systems using these Flatpak versions. The vulnerability affects only applications using the `persistent` permission (`--persist`).
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:NDebian
OSDebian11.0Flatpak
APPFlatpak1.14.0 – 1.14.10 (bez)1.15.0 – 1.15.10 (bez)
Related vulnerabilities
GNU Inetutils telnetd: ominięcie uwierzytelnienia przez zmienną USER
Sudo: eskalacja uprawnień do root poprzez opcję --chroot (CVE-2025-32463)
RCE przez deserializację PHP w Roundcube Webmail (parametr _from)
Erlang/OTP SSH — nieuwierzytelniony RCE (CVSS 10.0)
Apple WebKit: out-of-bounds write umożliwiający ucieczkę z sandbox przeglądarki