Flatpak 1.18.1 Patches 10 Critical CVEs — Including a Full Sandbox Escape to Host
On August 11, 2026, the Flatpak project released version 1.18.1 — a critical security update that patches ten CVEs at once, several of which are severe enough to deserve your immediate attention if you run Flatpak applications on Linux.
What Flatpak is and why this matters
Flatpak is the Linux application sandboxing and distribution framework used across Fedora, Ubuntu, Arch, and most other mainstream distributions. It promises that apps run in isolation from your host system — a sandbox. These vulnerabilities shatter that promise entirely.
The worst of them: a full sandbox escape
The most critical fix addresses CVE-2026-34078, a sandbox escape rated CVSS 9.3. The flaw lives in how the Flatpak portal handles paths in the sandbox-expose options. A sandboxed application can craft symlinks pointing anywhere on the host filesystem; when Flatpak mounts the resolved path inside the sandbox, the app suddenly has access to the full host — including system binaries, user home directories, and credential stores. From there, arbitrary code execution in the host context is feasible.
In plain English: any Flatpak app on your system could have read and written anywhere it wanted.
The rest of the ten CVEs
The other nine fixes address a layered set of additional privilege escalation paths, all described in the Linuxiac breakdown:
- Local root privilege escalation via symlink path traversal in
revokefsand commit tampering — a direct path to root. - Arbitrary root file writes in extra-data extraction, exploited through symlinks and path traversal.
- Another arbitrary file write in
flatpak build-initusing the same mechanism. - Symlink attack on
.ld.so, allowing files with arbitrary names to be written anywhere on the filesystem. - A downgrade loophole that let unprivileged users bypass safeguards and force-install older, potentially vulnerable app versions.
Concurrent releases: 1.19.0 pre-release also patched
Flatpak simultaneously pushed 1.19.0 (a pre-release branch) with the same security fixes, ensuring users on both the stable and development branches are covered. This simultaneous coordinated release is a signal of how serious the project considered these issues.
What you should do now
Update immediately. On most distributions, sudo apt upgrade flatpak, sudo dnf upgrade flatpak, or the equivalent will get you there. You can verify your installed version with flatpak --version — you want 1.18.1 or later.
If you use Flatpak in production or in any multi-user environment, treat this as an emergency patch. The scope of the vulnerabilities — full host filesystem access from any installed application — is about as bad as sandboxing failures get.
Flatpak's maintainers deserve credit for shipping a coordinated, comprehensive release rather than drip-feeding individual patches. Ten CVEs in one shot is a lot, but it is far better than discovering them one by one in the wild.