CVE-2026-86320: 
Linux Debian vulnerability analysis and mitigation

CVE-2026-86320 is a vulnerability in flatpak-builder that allows arbitrary host code execution via git hooks during module source extraction. When use-git-am: true is enabled for a patch source, flatpak-builder invokes git am without disabling git hooks, enabling a malicious source to execute arbitrary code on the host. Affected versions are >=0.99.2 and <=1.4.10; the issue is patched in version >=1.4.11. The CVE is currently in Reserved status, with the advisory published on September 12, 2026, and a CVSS category estimate of HIGH (GitHub Advisory, Feedly).

The root cause is classified as CWE-829 (Inclusion of Functionality from Untrusted Control Sphere). When use-git-am: true is set in a flatpak-builder manifest for a patch source, flatpak-builder calls git am to apply patches without passing flags (such as --no-verify) to suppress git hook execution. Because git runs unsandboxed in the host context at this stage, a malicious repository can include a post-applypatch hook in .git/hooks/post-applypatch that is automatically triggered upon successful patch application, executing arbitrary commands with the privileges of the host user running flatpak-builder. A public proof-of-concept demonstrating the full attack chain is included in the GitHub Security Advisory (GitHub Advisory).

Successful exploitation allows an attacker who controls a malicious source repository or manifest to execute arbitrary code on the host system with the privileges of the user running flatpak-builder. Since git operates outside the Flatpak sandbox during the build phase, there is no sandboxing boundary to limit the impact. This could lead to full host compromise, data exfiltration, installation of persistent malware, or lateral movement depending on the privileges of the build user (GitHub Advisory).

A public proof-of-concept script is included in the GitHub Security Advisory, demonstrating end-to-end exploitation. Exploitation requires that the victim use use-git-am: true in a flatpak-builder manifest pointing to an attacker-controlled or compromised source. No evidence of in-the-wild exploitation has been reported as of the advisory date. The CVE is currently in Reserved status, and no EPSS score or CISA KEV catalog entry is available at this time (GitHub Advisory, Feedly).

1. Prepare malicious repository: Create a git repository with a crafted post-applypatch hook in .git/hooks/post-applypatch containing the desired payload (e.g., a reverse shell or command execution script), and make it executable with chmod +x.
2. Package the repository: Archive the malicious repository as a tarball (e.g., tar -czf sample.tar.gz) and compute its SHA-256 hash for use in the manifest.
3. Craft a malicious manifest: Create a flatpak-builder JSON manifest that references the malicious tarball as a source, includes a patch file, and sets use-git-am: true for the patch source entry.
4. Deliver the manifest: Trick the victim into using the malicious manifest — for example, by contributing to an open-source project, submitting a pull request, or distributing the manifest through a package repository.
5. Trigger exploitation: When the victim runs flatpak-builder with the malicious manifest, git am applies the patch and automatically executes the post-applypatch hook on the host, running the attacker's payload with the host user's privileges (GitHub Advisory).

• File System: Presence of unexpected or recently modified files in .git/hooks/ directories within flatpak build working directories, particularly post-applypatch, pre-applypatch, or applypatch-msg hooks with executable permissions.
• Process: Unexpected child processes spawned by git or flatpak-builder during a build (e.g., shell scripts, curl, wget, nc, python, or other network/execution utilities).
• Logs: Build logs showing execution of git hooks during git am operations; unexpected output or errors in flatpak-builder build logs not attributable to normal build steps.
• Network: Outbound network connections initiated by git or shell processes during a flatpak-builder build to unknown external hosts (GitHub Advisory).

Upgrade flatpak-builder to version >=1.4.11, which addresses this vulnerability. As a workaround, avoid using use-git-am: true in manifests that reference untrusted or third-party sources. Additionally, performing builds inside disposable virtual machines or containers can limit the blast radius if exploitation occurs. Debian Linux users should monitor vendor advisories, as no vendor-supplied patch was available at the time of initial Feedly detection (GitHub Advisory, Feedly).

The advisory was published by maintainer bbhtt on the flatpak-builder GitHub repository on September 12, 2026. The severity was assessed as Low by the advisory authors, though Feedly's automated analysis estimates the CVSS category as HIGH. A Nessus detection plugin (ID 345679) was published by Tenable shortly after the advisory. No significant broader media coverage or notable researcher commentary beyond the advisory itself has been identified at this time (GitHub Advisory, Tenable).