Flatpak 1.18.1 has been released as a security-focused update to the popular Linux application sandboxing and distribution framework, addressing a substantial collection of vulnerabilities affecting sandbox isolation, filesystem access, privilege boundaries, and OCI handling.
The most critical fix in this release stops a sandbox escape that could let an app read and write anywhere on the host filesystem. Another key fix stops a local root privilege escalation caused by symlink path traversal in revokefs and commit tampering.
Moreover, the release fixes two other issues that could let files be written with root privileges: one in extra-data extraction using symlinks and path traversal, and another in flatpak build-init.
The update also brings several security fixes for OCI features. Developers fixed a hardlink path traversal bug during OCI archive extraction that could let attackers read any host file. They also fixed a buffer overflow in OCI delta stream path names on 32-bit systems.
Another fixed vulnerability was a symlink attack on .ld.so, which could let files with set names be written anywhere on the filesystem. Flatpak 1.18.1 also improves downgrade protection by closing a loophole that let unprivileged users bypass safeguards and downgrade installed apps.
Besides security fixes, this release includes regular bug fixes. It corrects a regression in environment handling for the portal’s flatpak-spawn feature and fixes problems with negated permission strings used in the allow and share run options.
The update also fixes a build failure when exporting metainfo releases.xml files, as well as crashes in the portal update monitor and OCI JSON processing. Now, Flatpak returns an error if file forwarding is tried with an empty path.
There are more improvements to OCI infrastructure. Now, the system helper verifies signatures using the mirrored repository instead of the lookaside server, TLS certificates are correctly used for OCI registry requests, and stream write failures are now passed on to curl.
For additional details, see the changelog. Most users will receive the update through their Linux distribution’s package repositories once maintainers package it.
