CVE-2026-34078: Flatpak has a complete sandbox escape leading to host file access and code execution in the host context
Flatpak is a Linux application sandboxing and distribution framework. Prior to 1.16.4, the Flatpak portal accepts paths in the sandbox-expose options which can be app-controlled symlinks pointing at arbitrary paths. Flatpak run mounts the resolved host path in the sandbox. This gives apps access to all host files and can be used as a primitive to gain code execution in the host context. This vulnerability is fixed in 1.16.4.
Security readout for executives and security teams
Plain-English summary
CVE-2026-34078 breaks Flatpak’s isolation. A malicious or compromised Flatpak app could make Flatpak expose arbitrary host paths into its sandbox, allowing access to host files and potentially code execution outside the sandbox. Flatpak versions before 1.16.4 are affected.
Executive priority
Treat this as urgent for Linux desktop or workstation fleets using Flatpak. The issue undermines a core security boundary and has critical severity, but current sources do not prove active exploitation.
Technical view
Before Flatpak 1.16.4, sandbox-expose options accepted app-controlled symlink paths. Flatpak resolved and mounted the host target into the sandbox, creating CWE-59/CWE-61 path-link handling exposure with high confidentiality, integrity, and availability impact.
Likely exposure
Linux systems using Flatpak versions earlier than 1.16.4 are the exposed population. Risk is higher where users can install or run untrusted Flatpak apps, or where Flatpak is relied on as a containment boundary for desktop applications.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. They do describe a complete sandbox escape primitive with host file access and host-context code execution potential, so absence of exploitation evidence should not lower remediation urgency.
Researcher notes
Focus validation on symlink handling around sandbox-expose portal options and host path mounting behavior. Avoid assuming every distribution is vulnerable at the same package version because vendors may ship backported fixes.
Mitigation direction
Upgrade Flatpak to 1.16.4 or a vendor-fixed backport.
Apply relevant Red Hat security advisories where applicable.
Prioritize endpoints that allow untrusted Flatpak app installation.
Limit Flatpak app sources to trusted repositories until patched.
Monitor vendor guidance for distribution-specific package status.
Validation and detection
Inventory installed Flatpak package versions across Linux endpoints.
Confirm Flatpak is 1.16.4 or vendor-marked fixed.
Check Red Hat CVE and errata status for affected fleets.
Review systems where Flatpak is used for application isolation.
Track CISA KEV and vendor advisories for exploit-status changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-59: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
3ADP providers
16Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-59 · source CWE mapping
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
UNIX Symbolic Link (Symlink) Following represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.