Flatpak 1.18.3 ships security fixes and repairs for build regressions
Flatpak 1.18.3 went out today, and it's the kind of release you quietly appreciate. No new features. No splashy demos. Just two security dependency updates and a batch of fixes for regressions that were quietly breaking local builds.
The fourth point release in the 1.18 stable line landed today, and per Flatpak's "immutable" policy, it's now locked to that version number and its original notes.
The security side is the headline
Flatpak normally bundles two dependencies you'd otherwise pull from the host, and 1.18.3 refreshes both to patched versions. bubblewrap moves to 0.12.0, closing off CVE-2026-87766. That tool is the heart of Flatpak's sandboxing, so anything that touches it matters. xdg-dbus-proxy gets bumped to 0.1.8 to address CVE-2026-93676, which controls how sandboxed apps talk to the host over D-Bus.
I'll be straight with you. The release notes don't spell out the technical details of either CVE. Flatpak references them by identifier and points you at the upstream advisories. The vulnerability database was unreachable during research, so the CVE numbers are really all we have to go on. If you want the exact exploit mechanics, you'll want to dig into the bubblewrap and xdg-dbus-proxy security pages directly.
Repairing the 1.18.2 damage
A good chunk of this release is triage. It fixes problems that showed up in the previous point release, especially on SELinux systems and when runtimes aren't installed per user.
The clearest case is issue #6818, reported on September 3 by a user called tleepa on Fedora 44. They hit a wall trying to build the Draw.io app. flatpak build-init --base simply failed with lsetxattr(security.selinux): Operation not supported. It only started working again after downgrading to 1.17.6. That's the kind of regression that turns a Saturday into a game of whack-a-mole with your own toolchain, so it's good to see it actually fixed.
A couple more fixes along the way
There's a subsandbox startup repair for flatpak-spawn (#6776). That's the command you use to launch host-side helpers from inside a sandbox, and it broke when an app was configured with --no-talk-name or --system-no-talk-name. The fix restores sane behavior under those restrictions.
Then comes a crash fix (#6842) for installs using explicit key bytes, which matters mainly for signed bundles. And because someone had to, the code of conduct and contributor guidelines picked up a few documentation and process updates as well.
Where 1.18.3 fits
The 1.18 line has been around since June 8, when 1.18.0 landed with better flatpak-coredumpctl handling, AMD's /dev/kfd compute support, and faster fish-shell startup. The next two points were heavier still. 1.18.1, on August 11, was genuinely security-heavy. It squashed ten advisories ranging from symlink attacks and local root escalation to buffer overflows in OCI delta streams. 1.18.2, two weeks later, leaned into correctness: GVariant validation, a system-helper crash fix, and a repair against older GLib builds.
1.18.3 keeps that maintenance cadence. As of this release there were 211 commits ahead on main, so the next point is coming whether you're watching or not. Keep in mind that Flatpak markets itself around the "build for every distro" promise, and releases like this one are what keep that promise from fraying for the people actually building runtimes.
How to update
Run your normal package manager or go through Flathub. If you build runtimes locally on SELinux, such as Fedora, or run non-per-user runtimes, you should pay a little more attention here since the build regression is what bites you. For everyone else, it's a routine bump you can schedule for a quieter day.
You can read the release notes, file a report in the issue tracker, and pull the older 1.18 point releases off the Flatpak GitHub page.
