CVE-2026-90616
7.4Flatpak · Flatpak
A symlink following vulnerability in Flatpak allows a malicious sandboxed application to gain arbitrary read and write access to host files, potentially leading to host-level code execution.
Executive summary
A vulnerability in Flatpak versions prior to 1.18.1 allows a malicious sandboxed application to escape its container and achieve arbitrary code execution on the host system.
Vulnerability
This is a symlink following flaw (CWE-61) occurring during the creation of sandbox app data directories. By manipulating symlinks in attacker-controlled path components, a local, unauthenticated sandboxed application can force the host to mount sensitive files into the sandbox environment.
Business impact
The ability for a sandboxed application to escape its container and execute code on the underlying host represents a critical failure of the security boundary. Given the CVSS score of 7.4, this high-severity flaw could lead to full system compromise, unauthorized data access, and the lateral movement of threats from a restricted application environment to the host operating system.
Remediation
Immediate Action: Update Flatpak to version 1.18.1 or later to implement the required symlink protection.
Proactive Monitoring: Audit system logs for unusual file access patterns or unexpected bind-mount operations initiated by sandboxed applications.
Compensating Controls: Ensure that Flatpak environments are run with the most restrictive permissions possible and avoid installing untrusted applications until the host platform has been patched.
Exploitation status
Public Exploit Available: Unknown
Analyst recommendation
Organizations utilizing Flatpak for application sandboxing must prioritize the upgrade to version 1.18.1 to eliminate this container escape vector. Because this vulnerability grants arbitrary host file access from within a restricted sandbox, it poses a significant risk to overall system integrity and should be addressed in the next scheduled maintenance window.
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section