CVE-2026-96807

Flatpak versions before 1.18.1 follow attacker-controlled symlinks when regenerating the dynamic linker cache for a sandboxed app: a malicious app can replace ~/.var/app/$appid/.ld.so with a symlink, causing Flatpak's regenerate_ld_cache routine to write its cache files at an arbitrary filesystem location. The write happens through normal app-launch/cache-regeneration flows, so no privileges or user interaction are required beyond the malicious app already being installed and run. What the attacker gains is limited: the filename and contents of the written files are not attacker-controlled, which the CVE description itself notes makes the flaw hard to exploit, so realistic impact is low integrity/availability impact (file clobbering or corruption) rather than straightforward code execution. Anyone running Flatpak before 1.18.1 on a Linux desktop with sandboxed apps installed is theoretically in scope, though exploitation depends on having a malicious app in place. No public proof-of-concept is known, this is not on the CISA KEV list, and no exploitation in the wild has been reported.

What to do: Upgrade Flatpak to 1.18.1 or later (or apply your distribution's backported security update) — the release notes indicate 1.18.1 fixes multiple vulnerabilities, so it is worth prioritizing. Verify with 'flatpak --version' on Linux desktops under management. Additionally, audit installed Flatpak apps and their remotes for untrusted sources, and check ~/.var/app/<appid>/.ld.so paths for unexpected symlinks, removing any found.