Flatpak EUVD-2026-88442

Requires the attacker-controlled Flatpak application to be installed or upgraded on the target system, and root-level file deletion only occurs for system-wide (as opposed to per-user) installations. Exploitation is therefore gated on administrator action installing/upgrading a malicious app (user interaction, UI:R) and on the system-wide installation mode for the highest impact; there is no remote network trigger despite the input's AV:N. It affects Flatpak versions before 1.18.4.

The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H, base 7.1) conflicts with the mechanics of the flaw: the attack requires a malicious Flatpak application to be installed or upgraded on the target, which is inherently a local, user/administrator-mediated action - not a network delivery. AV:N is almost certainly wrong; this should be AV:L with required user interaction (an admin installing the app). No EPSS score, no CISA KEV listing, and no public exploit code are provided, so exploitation is best described as no public exploit identified at time of analysis, though the flaw is a genuine privilege-boundary/sandbox-escape issue. The GHSA-5p67-xh8x-rq54 advisory and Red Hat entry confirm the vulnerability is vendor-acknowledged and patched (fixed in Flatpak 1.18.4). Realistically this is a real but conditionally-triggered privilege escalation: the impact is high (root-level arbitrary file deletion in system-wide installs) but the precondition - convincing an administrator to install a hostile app - meaningfully limits mass exploitation. It is a solid patch-soon issue rather than an emergency, absent any active-exploitation signal.

An attacker publishes a malicious Flatpak app (e.g. to a third-party repository or via social engineering) containing a crafted export/bin directory with symlink/path-traversal entries. When a victim installs or upgrades the app system-wide, Flatpak follows the traversal and deletes attacker-chosen files outside the deployment directory as root. No public proof-of-concept is referenced, so exploitation would require the attacker to build the malicious package themselves.